4 ms·
> 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 i
by BeetleB 6y ago
> 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).
- Sebb767 6y agoOn 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.
- dunefox 6y agoThere 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'.
- BeetleB 6y ago> 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.
- djaque 6y agoThe 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
- dunefox 6y agoIf 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.
- konjin 6y agoNo, 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.
- BeetleB 6y ago> 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.
- Jabbles 6y agoHow 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?
- konjin 6y agoThat'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.