Heck, I'm pretty terrified of the code written by CS professors.
One time I got a C code from one of the leading lights in machine learning, compiled it, ran it, and it segfaulted right away.
I started up the debugger, set a breakpoint in main() and it didn't even get that far.
I looked at the code and saw that he was statically allocating a 4GB array that he never used. I guess this didn't cause a problem on the 64 bit machine he was using, but it caused the code to blow up on 32 bit machines. I removed the array and it worked OK.
I was lucky to be programming in Java while it was still in beta when I was working on my PhD. One thing I noticed was that even the more computer savvy physics professors didn't get object orientation or any of the architectural concepts around it at all, so I was often called a "bad programmer" and told I should be more like somebody who cut his teeth on FORTRAN.
One time I got a C code from one of the leading lights in machine learning, compiled it, ran it, and it segfaulted right away.
I started up the debugger, set a breakpoint in main() and it didn't even get that far.
I looked at the code and saw that he was statically allocating a 4GB array that he never used. I guess this didn't cause a problem on the 64 bit machine he was using, but it caused the code to blow up on 32 bit machines. I removed the array and it worked OK.
I was lucky to be programming in Java while it was still in beta when I was working on my PhD. One thing I noticed was that even the more computer savvy physics professors didn't get object orientation or any of the architectural concepts around it at all, so I was often called a "bad programmer" and told I should be more like somebody who cut his teeth on FORTRAN.