How do you keep track of code experiments/spikes/side projects?

Question

I guess everybody has those. I certainly have them, lots and lots of small projects where I tried out some new technology/language/framework, or implemented some small idea with it, ordid some exploration on a dataset etc. They all live with dubious names in a folder in ~/dev and over time, I just forget about them. Sometimes I accidentally find them again when doing something related (same task, different tool, or so), sometimes not.Do you somehow keep track in a more elaborate way? Spreadsheet/database/notes?

withinboredom · Accepted Answer

I use InkDrop (InkDrop.app) to organize notes. I like it because it&rsquo;s GH flavored markdown, and when mixed with the prettier plugin it is amazing. Everything I write down (whether it&rsquo;s SQL queries or an internal doc) starts there. Every project idea starts there too. I have tags for &ldquo;project phases&rdquo; so I can go back and look at early thoughts of a project.It&rsquo;s not perfect, but it works for me.

raxxorrax · Answer

I do the same, I have this very unstructured folder. I have Gitea running on a server, but I create a repositories quite rarely, so the folder it is for now.Still works though if I remember that I looked into something. I wish I would take more notes though and if I do it is mostly text files withing project folders.