This is an expansion of a comment on Titus Brown’s blog post “Please destroy this software after publication. kthxbye.” which talked about how much work should go into software that was used in a submitted paper. In the past, I’ve thought of software as having one of two different purposes: Some software is just written for a single research purpose – this can be quick and dirty, as long as it does the immediate job.