Ask HN: Should I publish my research code?
> it's substantially more work to clean and organize the code for publishing, it will increase the surface for nitpicking and criticism (e.g. coding style, etc).<p>Matt Might has a solution for this that I love:  Don't clean & organize!  Release it under the CRAPL[0], making explicit what everyone understands, viz.:<p>"Generally, academic software is stapled together on a tight deadline; an expert user has to coerce it into running; and it's not pretty code. Academic code is about 'proof of concept.'"<p>[0] <a href="https://matt.might.net/articles/crapl/" rel="nofollow">https://matt.might.net/articles/crapl/</a>