Thanks for the link to the blog post! I vaguely remember that one but I don’t think I actually invested much time reading the auxiliary links. It makes a lot more sense now given the context.
I’m a big fan of ubiquitous capture and processing things ala the GTD system, but I use a more minimalist system when I code based on zen-to-done method and the Most Important Things. I understand not worrying about things until they matter, however I’ve found great value in capturing ideas and making decisions on what to do next given the various priorities on the project. Many of the ‘next two steps’ are pulled from the little brainstorms that happen during development or even when I’m thinking about things right before sleep / in the shower.
What do you do when you run across a bug or think of a neat thing to do while working on other issues/features? Do you keep a mental list in your head or just ignore them until they become painful?
A kanban/scrum system also helps when you have 3rd party demands since you can sort the cards relatively easily while they are in the back-log. Perhaps you don’t have those demands? We put a limit on the backlog in-lines with Joel’s ideas of software inventory once we have 20 or 30 items on the pending to-do, we have to sacrifice an idea before we commit to doing a new one.