I don't think searching for and showcasing someone'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 works and then later it can be refined, packaged up into modules, decoupled, optimized, etc.
Particularly for numerical and scientific work, there is a huge tradeoff between code cleanliness/readability and performance. I normally start by just copying the "demo algorithm" from a research paper straight into whatever language I'm using. The goal is to simply get the code working properly, and then I begin tweaking it for speed. Once it'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.
Particularly for numerical and scientific work, there is a huge tradeoff between code cleanliness/readability and performance. I normally start by just copying the "demo algorithm" from a research paper straight into whatever language I'm using. The goal is to simply get the code working properly, and then I begin tweaking it for speed. Once it'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.