News for hackers. Stuff that matters.
Re:Why bad scientific code beats code following "best practi... by danso on Monday May 12, 2014 @06:04AM (#7731897)
> Oh, and one really mean observation that I'm afraid is too true to be omitted: idleness is the source of much trouble. A scientist has his science to worry about so he doesn't have time to complexify the code needlessly. Many programmers have no real substance in their work - the job is trivial - so they have too much time on their hands, which they use to dwell on "API design" and thus monstrosities are born.

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.

Re:Why bad scientific code beats code following "best practi... by adamors on Monday May 12, 2014 @06:20AM (#7731936)
The entire post reeks of ignorance. I don't understand how it got to the front page.
Re:Why bad scientific code beats code following "best practi... by c_plus_minus on Monday May 12, 2014 @10:51AM (#7732991)
Totally agree. Seems he has a bit of a chip on his shoulder, by frequently mentioning "software engineering" in quotes.

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 :)

Re:Why bad scientific code beats code following "best practi... by spacemanmatt on Monday May 12, 2014 @07:14AM (#7732048)
Seriously. It seems like there have been more neophytes willing to come out against mature practice like factory methods and other artifacts of polymorphic architecture. Oh well, complaining probably triggers a seratonin release or something for them.
Re:Why bad scientific code beats code following "best practi... by TillE on Monday May 12, 2014 @08:10AM (#7732243)
"Hey look, it's possible to misuse design patterns! Don't they suck, amirite guys?"

Online forums are generally filled with programmers who have never written anything large and complex.

Re:Why bad scientific code beats code following "best practi... by spacemanmatt on Monday May 12, 2014 @09:20AM (#7732496)
Even worse: "Hey look, it's possible to be confused by design patterns! Don't people who use them suck, amirite guys?"

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.

Re:Why bad scientific code beats code following "best practi... by ams6110 on Monday May 12, 2014 @07:29AM (#7732096)
I know a lot of programmers who don't really do much real work. In particular one place that I worked they seemed to spend half the day promoting recycling, drinking water, and eating healthy; taking walks; playing chess; napping; talking about stand-up desks, etc. Maybe the OP works/has worked in a place like that.
Re:Why bad scientific code beats code following "best practi... by collyw on Monday May 12, 2014 @11:10AM (#7733138)
Actually that sounds a bit like the bioinformaticians in the last pace I worked. They would write a script that took 3 hours to run, launch it, and play on facebook for until it complete. (They could have learned to use a debugger / IDE /library that would have improved their efficiency - I don't think any of them used "advanced tools" like those). As the database programmer I always had too much work to slack off like that.

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.

Re:Why bad scientific code beats code following "best practi... by collyw on Monday May 12, 2014 @07:16AM (#7732055)
Most of the bioinformatics I work with write short scripts to count thing up (and some need my help to write a couple of nested loops after doing it for 4 years). Hardly difficult stuff.
Re:Why bad scientific code beats code following "best practi... by danso on Monday May 12, 2014 @07:42AM (#7732140)
Yes, some tasks can be done very simply, and decent programmers know this. I've written lots of Twitter-accessing code to do data analysis, but I love using the ruby-t gem, which lets me in a single line of UNIX (with pipes) do something like unfollow every user I currently follow who tweets more than 50 times/day and doesn't follow me back.

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.

Re:Why bad scientific code beats code following "best practi... by danieltillett on Monday May 12, 2014 @08:06AM (#7732228)
I was I the same department as Neil when he gave this presentation - it is an amazingly small world at times.
Re:Why bad scientific code beats code following "best practi... by danso on Monday May 12, 2014 @08:12AM (#7732254)
Ha! That's funny...I don't know him at all, and have no idea whether he is actually well-known or well-regarded, given that he's not a social-media-celebrity or whatnot...but I stumbled upon his blog years ago while searching for various scraping techniques, and even as an engineer, reading his blog was a revelation for me that scientifically-minded, rigorously-logical people may yet still have a blind spot towards process.
Re:Why bad scientific code beats code following "best practi... by danieltillett on Monday May 12, 2014 @08:24AM (#7732294)
He is a funny character, but quite serious. I know he had lots of problem dealing with all the biologists in my old department.