[tachyonbeam]

That's very similar to what I do. I have a TODO list that includes notes, and big features that I break down into very small tasks. I can get back where I was on a project in just one minute, because the TODO list tells me.

When debugging a difficult issue, I also take notes about my findings, and ideas of directions to investigate next.

[blackflame7000]

I also do something similar with a TODO list however I haven't figured out a good solution to organize it. For example lets say i'm working on feature A and then B. During the developement of A, I find I also need C & D so I add them to the TODO list which now looks like ABCD when the actual development order needs to be ACDB. This cause my TODO list to become quickly out of sync with the order in which things need to be done. With long lists of inter-dependencies, have you found a good method of keeping your TODO list from jumping all over the place?

[tachyonbeam]

I reorder the items periodically. When I start my day, I make a plan for what I'd like to achieve, and organize it based on priorities, dependencies, and also what I feel like doing. If I'm tired and can't concentrate well one day, I will take on smaller and easier tasks.