Tracking project-specific tasks is something I've changed many times over the years. I've tried apps like Taskwarrior (which I loved), using in-line TODO comments throughout my code and collecting them with something like magit-todos, to now just a strategically-named plain org file I can just spawn when I need it. And recently I got a bug to try something new. I'm writing this post in parallel of me trying to implement it so it follows my train of thought and trials.

For as long as I can remember, I've tried to find a workflow that fits in my brain. I have usually settled with a massive ~/code directory, as we do, and try to manually manage the directories for whatever I'm working on. Often times I'd have multiple related projects cloned that would have to be merged together. Over time, this ends up being a massive, unmaintainable mess where I have to periodically spend time investigating old project directories and try to remember if anything in there was important before I blew it away to prune down the sheer amount of projects that have built up.

You don't need a lab Ben Whitley purplg.dev Why is self-host? Big service providers can and have lost your data. Requiring an internet connection to turn on your light while you're home is asinine. Privacy, of course. Is it expensive? No! But it can be if you like. My setup involves a $10/mo and $5/mo Linode VPS. One hosts my own Matrix (Synapse) server and an IRC bouncer and the other is other random small services like an always-online Syncthing peer.

https://xkcd.com/378/ Interesting video on the history of Emacs: https://youtu.be/8dpnow-j000 Me Ben Whitley github.com/purplg Just someone who loves computers. I have a tendency to move fast (sorry!), so please remind me to slow down if I go too fast. What is Emacs? Emacs is a Lisp engine that was turned into an editor. The core is written in C but most of it is written in Emacs Lisp. This enables you to change pretty much anything about it at runtime.