News for hackers. Stuff that matters.
Re:Publish your computer code: it is good enough by whyenot on Wednesday October 13, 2010 @09:09PM (#1789477)
A lot of code in the sciences is used once or only a few times. You crunch the data, write the paper and move on to the next research project. You don't get tenure for writing unit tests.
Re:Publish your computer code: it is good enough by _sh on Thursday October 14, 2010 @01:52AM (#1789964)
And you don't make friends with salad, i.e. you certainly won't make tenure when your paper is demonstrated as flawed due to errors in crunching the data that would have turned up with testing.
Re:Publish your computer code: it is good enough by joe_the_user on Thursday October 14, 2010 @02:13AM (#1789995)
Ah,

and that brings us back to why many scientists don't publish at all now...

As long as not publishing code is standard, there's a incentive to do it since it might open you to career-withering criticism...

Re:Publish your computer code: it is good enough by nervechannel on Thursday October 14, 2010 @03:05AM (#1790104)
Consider this though:

I have tried to explain (With limited success) to my colleagues in bioinformatics that not unit-testing your code is like using an instrument that hasn't been calibrated, and blindly trusting the results to be right.

Re:Publish your computer code: it is good enough by jonhendry on Thursday October 14, 2010 @11:25AM (#1791208)
They may not unit test it, in the software development sense, but they probably hand-check a new bit of calculation code on a few data points before setting it loose on a whole data set.
Re:Publish your computer code: it is good enough by nervechannel on Thursday October 14, 2010 @01:27PM (#1791723)
Yes, or sometimes even less rigour than this: run some data and see if the results "look right".

This is the standard procedure for when you've developed a complex algorithm to do something novel, and actually working through it by hand would take hours.

I should know, this is how I used to do it before I knew better, and as a result one of my published papers has (very slight) numerical errors in.