And as someone who had the grave misfortune of having some experience in scientific code, all I can do is laugh at the OP's link. Yeah sure, scientist's are great at programming. I say let them off at it, because I want nothing to do with it. I value my sanity too much :)
Online forums are generally filled with programmers who have never written anything large and complex.
The whole internet is amateur hour. I just got caught in a daydream, pretending like HN was above the noise for a while. Maybe it was.
Another point, is that when I have to make a bigger architectural decision, then I don't jump straight in and code. I usually come up with two or three possible solutions in my head (or on a piece of paper). I will stare at the wall for most of the afternoon, go for walks, as I play the ideas off against each other. After a day or two I usually have an idea of which solution is better, and why.
The OP is railing against dumb programmers...OK, that's fine. But just because I've heard of Josef Mengele doesn't mean that it's a good use of time to continually rant about the dangers of science.
Speaking of bioinformatics, one of my favorite programming blogs is from bioinformatics scientist Neil Saunders, who writes about scripts, complex and short, that he uses to data munge and efficiently run experiments. The title of his blog was inspired by an encounter he had with a fellow scientist who did not see the value of programming:
http://nsaunders.wordpress.com/about-2/about/
> You may be wondering about the title of this blog.
Early in my bioinformatics career, I gave a talk to my department. It was fairly basic stuff – how to identify genes in a genome sequence, standalone BLAST, annotation, data munging with Perl and so on. Come question time, a member of the audience raised her hand and said:
“It strikes me that what you’re doing is rather desperate. Wouldn’t you be better off doing some experiments?”*
It was one of the few times in my life when my jaw literally dropped and swung uselessly on its hinges. Perhaps I should have realised there and then that I was in the wrong department and made a run for it. Instead, I persisted for years, surrounded by people who either couldn’t or wouldn’t “get it”.
Ultimately though, her breathtakingly-stupid question did make a great blog title.
Jesus, seriously? Can't tell if the author is just trolling flippantly in response to what may have been an unfair post...but ignoring the "programmers have no real substance in their work" thing...the OP mistakes thinks that "science" is all one needs to keep something on track. Uh, no. Just because someone thinks they know what they're doing scientifically doesn't mean they are good at examining or scrutinizing the way they work...which can include everything from the efficiency of data collection to the accuracy of such measurements. A good software engineer is not just fluff in such a situation.