11–20 of 34 posts
Three lists: TODO, DOING, DONE
Items in DONE get archived the next day. Items in DOING get moved back to TODO if not completed. I organise them in their list by importance - i.e. ones at the top are most important.
I use labels pretty heavily too such as red for BLOCKED.
[Inbox][Queue][This Week][Today][Done][Done Apr 2nd]
Text files version controlled in git:
/notes/
/notes/project1/todo.txt
/notes/project2/todo.txt
/notes/project3/todo.txt
Creating Todos is pretty easy; i can create as many as I want at once via an email or entry in the search.
Categorizing them is the next trick: I get emails every other day for todos I created that aren't classified yet.
After that, they get regularly reviewed and timestamped as reviewed so they don't need to reappear for a while. I get emails for any todos that have never been reviewed, or that are overdue for a review.
When I'm deciding what to do in the next i select several I think I can tackle and add them to my list of active todos, then sort them based on priority.
Anything with a due date gets noisy (pesters me via email) as the date approaches as well as if its overdue; until it's removed or completed.
I could but haven't needed to use contexts yet or time estimates; primarily it's been a matter of making sure something is at least in the system and being tracked/reviewed in a way that I can forget about because I know it remembers and will remind me through a variety of ways.
I also get a weekly report of open todos, new todos, and other statistics.
This works for me, because it is easy to do brain dumps of this or that, while also making it harder for me to drop a particularly important ball, or lose track of it.
I use it mainly to track ALL of the things that is going on at work.
Todos with timeframes and deadlines get done. So I peruse the todo list and set their timeframes. I use Google Calendar to schedule them.
I keep a repo on all my systems that track a Gitlab repo (any Git repo would work). This repo contains a primary ToDo file with an overall list. When necessary, I spawn dedicated lists for specific projects or events. This is all written in Markdown (usually Github flavored).
The text editor is left to the reader's preference :) I'm strongly preferential of Vim, and use a few different Markdown plugins to ease writing.
Occasionally, if needed I build a printable PDF using Pandoc. Usually I only do this when I need to bring it with me.
Of course this doesn't bring any sort of notifications or reminders, so I supplement this with Google Calendar (and more recently Google Keep) when needed.