4 ms·
The most compelling reason I've heard against releasing code is to encourage independent implementations. While others may find bugs in released code, they may
by tensor 7y ago
The most compelling reason I've heard against releasing code is to encourage independent implementations. While others may find bugs in released code, they may also just use it as is extending it to test new ideas.
This could propagate any bugs in the code to multiple works. A similar problem occurs with blog code snippets that are written with shortcuts. Despite warnings that these snippets need to be expanded for production settings they are often copy pasted as is into hundreds of code bases, propagating incomplete or buggy code.
Still, you could solve for this in other ways. E.g. maybe reproduction focused journals can require reimplementation.
- anarchodev 7y agoYes and this already happens — check out the “cluster failure” paper documenting bugs that have been baked into statistical processing packages for fMRI analysis for years. Whole fields of science having no doubt already been built on top of these bugs, now might be a good time to start writing unit tests.