News for hackers. Stuff that matters.
Re:Challenge to scientists: does your ten-year-old code stil... by BeetleB on Monday August 24, 2020 @11:28AM (#24261579)
> their job is not coding

To me, that's like a theoretical physicist saying "My job is not to do mathematics" when asked for a derivation of a formula he put in the paper.

Or an experimental physicist saying "My job is not mechanical engineering" when asked for details of their lab equipment (almost all of which is typically custom built for the experiment).

Re:Challenge to scientists: does your ten-year-old code stil... by Sebb767 on Monday August 24, 2020 @11:42AM (#24261707)
On one hand, yes. But on the other hand, reuseable code, dependency management, linting, portability etc are not that easy problems and something junior developers tend to struggle with (and its not like that problem never pops up for seniors, either). I really can't fault non-compsci scientist for not handling that problem well. Of course, part of it (like publishing the relevant code) is far easier and should be done, but some aspects are really hard.

IMO the incentive problem in science (basically number of papers and new results is what counts) also plays into this, as investing tons of time in your code gives you hardly any reward.

Re:Challenge to scientists: does your ten-year-old code stil... by BeetleB on Monday August 24, 2020 @11:55AM (#24261844)
> But on the other hand, reuseable code, dependency management, linting, portability etc are not that easy problems and something junior developers tend to struggle with

On the original hand, these are easier problems than all the years of math education they have. Once you're relying on simulations to get results to explain natural phenomena, it needs to be put on the same pedestal as mathematics.

Re:Challenge to scientists: does your ten-year-old code stil... by dunefox on Monday August 24, 2020 @11:48AM (#24261764)
There are tons of tutorials on using conda for dependency management, it's not rocket science. And using a linter is difficult? If a scientist needs to read and write code as part of their job then they should learn the basics of programming - that includes tools and 'best practices'.
Re:Challenge to scientists: does your ten-year-old code stil... by djaque on Monday August 24, 2020 @11:46AM (#24261744)
The point is that as a scientist your code is a tool to get the job done and not the product. I can't spend 48 hours writing unit tests for my library (even though I want to) if it's not going to give me results. It's literally not my job and is not an efficient use of my time
Re:Challenge to scientists: does your ten-year-old code stil... by dunefox on Monday August 24, 2020 @11:51AM (#24261810)
If the code you base your work on is horrible it definitely makes me question your results. That's why it's called the reproducibility crisis.

Writing some tests, using a linter, commenting your code, and learning about best programming practices doesn't take long and pays off - even for yourself when writing the code or you need to touch the code again. "48 hours writing unit tests" is a ridiculous comparison.

Re:Challenge to scientists: does your ten-year-old code stil... by konjin on Monday August 24, 2020 @09:29PM (#24267357)
No, the reproducibility crisis is that when 10 people write the same library you all get different results.

This is just complaining that science is too hard because you can't be bother to replicate an experiment.

Re:Challenge to scientists: does your ten-year-old code stil... by TimothyBJacobs on Monday August 24, 2020 @11:59AM (#24261896)
This is the same as any other argument against testing. Unless you are actually selling a library, code is not the product. Customers are buying results, not your code base. Yet, we've discovered the importance of testing to make sure customers get the right results without issues.

If you want your results to be usable by others, the quality of the code matters. If all you care is publishing a paper, then I guess sure it doesn't matter if anyone else can build off your work.

Re:Challenge to scientists: does your ten-year-old code stil... by PeterisP on Monday August 24, 2020 @02:11PM (#24263546)
But the results are usable by others, in most fields of science the code is not part of these results and is not needed to enjoy, use and build upon the research results.

The only case where the code would be used (which is a valid reason why it should be available somehow) is to assert that your particular results are flawed or fraudulent; otherwise the quality of the code (or its availability, or even existence - perhaps you could have had a bunch of people do all of it on paper without any code) is simply irrelevant if you want your results to be usable by others.

Re:Challenge to scientists: does your ten-year-old code stil... by BeetleB on Monday August 24, 2020 @02:27PM (#24263753)
> The only case where the code would be used (which is a valid reason why it should be available somehow) is to assert that your particular results are flawed or fraudulent;

Not true. Code is often used and reused to churn out a lot more results than the initial paper. A flaw in the code doesn't just show one paper/result as problematic. It can show a large chunk of a researcher's work in his area of expertise to be problematic.

Re:Challenge to scientists: does your ten-year-old code stil... by BeetleB on Monday August 24, 2020 @11:53AM (#24261829)
> The point is that as a scientist your code is a tool to get the job done and not the product.

Everything you say is as true for experimental equipment and mathematical tools. Physicists are fantastic at mathematics, yet are one of the most anti-math people I know - in the sense of "Mathematics is just a tool to get results that explain nature! Doing mathematics for its own sake is a waste of time!"

The equation is not the product - the explanation of physical phenomena is. If the attitude of "I don't need to show how I got this equation" is unacceptable, the same should go for code.

Re:Challenge to scientists: does your ten-year-old code stil... by RandoHolmes on Monday August 24, 2020 @12:10PM (#24262016)
> I can't spend 48 hours writing unit tests for my library

No one is insisting on top quality code, but there has to be an acceptance that code can be flawed and that needs to be tested for.

Re:Challenge to scientists: does your ten-year-old code stil... by Jabbles on Monday August 24, 2020 @11:57AM (#24261880)
How do you know it won't give you results? Maybe it will find a bug that would have resulted in an embarrassing retraction.

Maybe it wouldn't find any bugs, but give confidence to and encourage other users and increasing your citations and "impact".

Maybe it will just save you 48h later on when you need to adapt the code.

Software engineering has generally accepted that unit testing is a good practice and well worth the time taken. Why do you think science is different?

Re:Challenge to scientists: does your ten-year-old code stil... by dunefox on Monday August 24, 2020 @02:07PM (#24263486)
> Why do you think science is different?

It's really not, I guess his focus lies on cranking out irreproducible papers.

Re:Challenge to scientists: does your ten-year-old code stil... by konjin on Monday August 24, 2020 @09:27PM (#24267344)
That's literally what they do.

Theoretical Physicists (literal conversation I had):

>Yeah, this looked like it simplifies to 1-ish and Smart John said it's probably right.

Experimental physicists (another literal conversation):

>Yeah, we build it with duck-tape and there's hot glue holding the important bits that kept falling off. Don't put anything metal in that, we use it as a tea heater, but there's 1000A running through it so it's shoots spoons out when we turn the main machine on.