3 ms·
Typically I have a little to-do list on paper where I write down what needs to be done to implement a certain feature. I stike out the things I have completed a
by Archelaos 6y ago
Typically I have a little to-do list on paper where I write down what needs to be done to implement a certain feature. I stike out the things I have completed and add new items on the go. Sometimes the to-do list is ordered (eg. when implementing a step-by-step algorithm); most of the time it is just a few unordered items. When I stop in the middle of such an item, I typically use the same technique as you: I add an invalid line of code, probably with a small note in the source code.
- padraigf 6y agoYes, this is a good practice whether you're leaving for the day or not. See David Allen's book 'Getting Things Done'. A central principle of it is: the place for your todo list is on paper (or some repository), not in your head. This clears your head for focusing on the immediate task at hand. So can be helpful for getting into a flow-state during the day, as well as between days.
- lcall 6y agoAgreed. I gradually morph that to-do list into pseudocode and that into code, sometimes in a comment block. When in the code and need to jump around different thoughts all in progress, I also tend to put "%%" and/or "%%$%" as a marker for "come back to this". (It helps that it doesn't compile, and works across platforms or different editors, so I don't have to change the habit over time.)