News for hackers. Stuff that matters.
Re:To don't (2012) by jerf on Thursday April 17, 2014 @10:51AM (#7603914)
I've had success with leaky todo lists. Basically, write yourself a todo list for, say, today, then at the end of the day, trash it, pretty much regardless of how far you made it. If a task is to survive the next day, it should get there "organically" rather than by being blindly copied. If you find yourself copying a task more than three or four times, that's a clue to drop the priority. (Only a clue. Sometimes things happen that don't really release you from any todo obligations, like sick kids, but it's still at least a clue.)

Though I tend to find this is more useful for weekends when I have to figure out what maintenances tasks to do than anything to do with programming.

For development, another approach is to just learn to live with the Katamari ball. Yes, my project has about 1500 open "bugs"/issues. That's life. The only todo-ed-ness that I accept is that I need to at least look at the incoming list and deal with them somehow, but "clearing the list" isn't on the table, so why stress about it at all? Some people can't seem to do this, so they'll have to seek other solutions, but this works for me.

There are no comments on this comment yet.