Programming, like writing, is deliberating over several rabbit holes. If you don't write down why you did or didn't do something, you're doomed to repeat the de

Programming, like writing, is deliberating over several rabbit holes. If you don't write down why you did or didn't do something, you're doomed to repeat the deliberation a week from now. Also worth recording are throwaway code snippets and gnarly awk-sed invocations. A plaintext file is sufficient. I noticed every programmer who even mentions zettlekasten produces bad, verbose code. Fortunately, obsessing over note taking naturally limits how much bad code he produces.