Ask HN: Should I publish my research code?
The Carpentries[0] provide some great resources and training for academics who are interested in this. Check out Software Carpentry[1] and Data Carpentry[2] in particular.<p>Publishing research code is admirable, and in an ideal world everybody would publish their code and data. That said, we shouldn't pretend that there aren't tradeoffs. Time spent polishing your code to make it presentable is time not spent on other aspects of your research. Time spent developing software development skills is time that could be spent learning new research techniques (or whatever). Reproducible research is great, but it's certainly possible to take it too far at the expense of your productivity/career.<p>You should also take your own personality into account. If you're a perfectionist you might struggle to let yourself publish research-quality code rather than production-quality code and consequently over-allocate the time you spend prettying up your code.<p>[0] <a href="https://carpentries.org/" rel="nofollow">https://carpentries.org/</a><p>[1] <a href="https://software-carpentry.org/" rel="nofollow">https://software-carpentry.org/</a><p>[2] <a href="https://datacarpentry.org/" rel="nofollow">https://datacarpentry.org/</a>