Timeline for How should I remember what I was doing and why on a project three months back?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2014 at 11:34 | comment | added | Martin Gjaldbaek | I've found that the nested to-do lists that are so easily done with workflowy.com fit my mental model when programming better than a plain to-do list. They just map so well to a program's multiple layers of abstraction and subcomponents and thus to the corresponding tasks to work on these. | |
| Nov 15, 2014 at 19:08 | comment | added | macintux | I've found the concepts described at bulletjournal.com quite useful for capturing my daily activities and needs | |
| Aug 19, 2014 at 17:00 | comment | added | Laconic Droid | I have tried a number of GTD apps, but for me, a paper notebook is still the most useful. Every day, I log the date and keep notes of salient points as the arise. If there is anything I need to take care of the following day, I mark it as !!task!! or similar so it's easy to pick out when I'm skimming. Colour coding also works well (if you are consistent). | |
| Jul 22, 2014 at 20:40 | history | edited | Scott Whitlock | CC BY-SA 3.0 | added 243 characters in body |
| Jul 22, 2014 at 16:15 | comment | added | Scott Whitlock | @BartvanIngenSchenau - yes, I was generally thinking of smaller single-person projects where a single developer would be bouncing among many projects, but in a larger team-based project you need a better system for tracking and managing to-do list items. | |
| Jul 22, 2014 at 15:17 | comment | added | tzerb | If you want to take it a bit further, you might want to look at a system like David Allen's GTD. | |
| Jul 22, 2014 at 14:57 | comment | added | SimonGates | trello.com is a life saver. Even for those Monday Monring team meetings where I struggle to remember what I did last week and what I should be working on this week. Its also free. | |
| Jul 22, 2014 at 13:29 | comment | added | Blrfl | TODOs in the code are excellent, but you have to be diligent about putting them there, even for teeny little things. Having a todo target in your makefile that dumps them out is also useful. | |
| Jul 22, 2014 at 13:20 | comment | added | Joeri Sebrechts | Indeed. Always park downhill. It's a matter of habit. I never leave a codebase without making a note for myself in the code or in my todo list on what to do next. I also make sure that everything I know I still have to do is in a todo either in the source (I use the TODO: convention in comments which my IDE can detect and present as a list), or in my separate todo list (I have just the one for all projects, but it is categorized and prioritized). | |
| Jul 22, 2014 at 12:11 | comment | added | Bart van Ingen Schenau | And if you are working on an agile project with small tasks, the backlog should be your primary to-do list for that project. | |
| Jul 22, 2014 at 12:09 | history | answered | Scott Whitlock | CC BY-SA 3.0 |