I don&#x27;t think searching for and showcasing someone&#x27;s old, exploratory code really demonstrates much.  A lot of my initial code for studying new concepts is atrocious — inefficient, memory-wasting, overly verbose; the point is to just get something that <i>works</i> and then later it can be refined, packaged up into modules, decoupled, optimized, etc.<p>Particularly for numerical and scientific work, there is a huge tradeoff between code cleanliness&#x2F;readability and performance.  I normally start by just copying the &quot;demo algorithm&quot; from a research paper straight into whatever language I&#x27;m using.  The goal is to simply get the code working properly, and <i>then</i> I begin tweaking it for speed.  Once it&#x27;s optimized though, the result usually looks nothing like the original algorithm and it is difficult to tell what the code is doing just by looking at it.