|
|
|
|
|
|
by neilv
1786 days ago
|
|
|
For personal (non-work), I've been using a modified version of todo.txt (http://todotxt.org/) text-file format successfully for 2+ years, and found my setup doesn't have some of the problems the article raises (though other problems aren't problems for me). My tweaks to todo.txt, and some helpful Emacs Lisp, is at: https://www.neilvandyke.org/todotxt/ For work project management, I'm recently using GitLab Issues and Board, with my own labels for urgency and Kanban state. (This isn't quite enough for large project planning, for which I usually use Gantt heavily. But hopefully the next time I need that, there'll be an easy way to link the work breakdown structure and dependencies to all the GitLab-based data capture and workflow the team is doing.) |
|
|
* It seems you use your list for scheduling as well. I prefer to just use a calendar (calcurse) for this kind of things, I only use dates in my TODO list to know when the item was created, so that I can reevaluate it if I see it stays there for too long (and you can have a cronjob for that).
* I use different lists for inbox and waiting. Depending on how you display your tasks (you can just avoid showing the @waiting ones), that could be the same result. I prefer to have smaller lists (i.e. getting an empty main list means I'm really done and I can see what I wanna do next).
* I tend to use priorities instead of your @then, but that's also not nice. Or I just don't append it to the list: I can do that once I have completed the current task, and maybe I'll have to revisit. If it's something complex enough, it should be documented elsewhere anyway.
* People are also contexts to me, I just use a prefix, e.g. @p_neilv.