Hierarchical-Data

On the fungibility of time Now, unless you have a strict timetable - you still have a choice of when to place things in your schedule. As in a choice on what todo next. This makes this first tool useful: you’d want to fetch things that need done anyway in the future (especially if small/short) - today. Now, if possible (if you have room for them now). This clears your future schedule for big blocks - lowering the entropy of future schedules. Less tasks switching, or, who knows, even a few vacation days. Even a little bit of collecting together all needed information (links, emails, documents, addresses, maps) for the upcoming big push, ahead of time - will yield a feeling of being in control - and a warm start for the upcoming work block. ...

As simple as you need to - but not simpler Organizing system is a process running in the background - while you try to accomplish real work. It’s supposed to help - not require full attention. It should be able to degrade gracefully under pressure and chaos - and recover later easily. Ad-hoc method: Low/High Watermarks The setup is that you don’t really have enough time for a Mind Dump - nor walk a full GTD system and reviews. But you want to keep things together and remain in control. At least apparently. One easy way is to keep a running list of areas - and mark them with one of 3 labels: ...

Adding Estimates to DevTodo2: A Journey in Go and Hierarchical Tasks Intro Some time ago we went on adapting devtodo2 as an internal tool to allow task estimates and parent summaries. The core appeal of devtodo2 is its simplicity: it’s a command-line utility where task lists are stored as a simple .todo2 file right in your project folder. This makes it incredibly handy to have a project’s todo list and completion history live alongside the code, effectively mitigating the “forgetting what’s been done” (or the Zeigarnik effect)—where unfinished tasks clutter the mind, but completed ones vanish from memory. ...