Ask HN: How do you keep track of code experiments/spikes/side projects?
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?
4 comments
[ 285 ms ] story [ 868 ms ] threadIt’s not perfect, but it works for me.
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.