2 ms·
I would regard (from experience) "science ready" code as something that you run just often enough to get the results to create publications. Any effort to get
by arethuza 6y ago
I would regard (from experience) "science ready" code as something that you run just often enough to get the results to create publications.
Any effort to get code working for other people, or documented in any way would probably be seen as wasted effort that could be used to write more papers or create more results to create new papers.
This kind of reasoning was one of the many reasons I left academic research - I personally didn't value publications as deliverables.
- gowld 6y agoIf your experiment is not repeatable, it's an anecdote not data. Any effort to write a paper readable for other people, or document the experiment in any way would probably be seen as wasted effort that could be used to create more results. The "don't show your work" argument only makes sense if you are doing PR, not science.
- neutronicus 6y agoIf it's repeatable by you then it's a trade secret, not an anecdote
- arethuza 6y agoI specifically got told off by my supervisor for trying to "improve" some of the software we were working on!
- chriswarbo 6y agoMy experience has been similar. Still, there's plenty of room to encourage good(/better) practices which cost essentially nothing, e.g. using $PWD rather than /home/bob/foo