Skip to main content

A tale of three TODO products

I'm the kind of guy that hates the amount of time he spends considering, evaluating, and test driving new productivity software. Recently I had yet another surge of uncertainty over my use of Remember The Milk, and I tried a few other things. I gave a spin on Nozbe and Todo.txt, and I've come to a conclusion.

For now...

I have been a big fan of Remember The Milk, and I pay for a professional account. Even still, I'm not above admitting I might be wrong, so when a few things started to annoy me I sought out something new. I had heard Todo.txt talked up a lot on This Week in Google, given that the author is a host on the show. I had also tried Nozbe in the past, but new it had several large updates since then and wanted to give it another try.

Remember The Milk

I really was happy with RTM, so I want to make clear the things I do like about it! I really have been happy with the Android app, and with the use of smart lists to create filters that match different contexts I want to work in. Here is the corner stone of my smart lists, which I combine with several others:

(dueBefore:"tomorrow midnight" OR (due:never AND tag:next) ) OR (dueWithin:"1 month of today" AND tag:bill) OR (tag:writing AND dueWithin:"1 week of today") OR (tag:sticky)

This means "Everything with a due date that is today or already passed, or without a due date marked to be done next, or due within the next month and is a bill, or is something i need to write within the next week, or is tagged 'sticky'" and I can update this as need be, and other lists that use it adjust themselves. What this lets me do is set due dates in the future and hide the items until they become important, so it works great for setting my todo list for work and to see a condensed set of things I should focus on each day.

So, what was getting on my nerves? What I haven't gotten to feel right is a small and loose set of tasks that I want to do in order, and so only one is relevant at a time. Good example is a book series. I need to maintain next tags on items right now, and that isn't terrible, but automation is great. What I feel would be nice is a tool where lists were super light and throw-away and only the top item on the list was included in the main view, as a "Next Action". Yes, that is a GTD thing.

Todo.txt

I can't say the idea of keeping everything in a file I own isn't appealing, it is. I was able to customize the sorting command and some filtering options so I could kind of do a thing like the next actions I talked about before, and I could see the first thing in each context I've defined when I list my tasks. But, that flexibility kind of vanishes when I use the android app, so while it is very cool that it just syncs my local file via Dropbox, it also means that I can only customize half my experience, which kind of just makes the android half feel worse. At least my smart lists work in RTM's android app.

Nozbe

The most appealing feature here is an actual support for next actions. With any list, anything marked as a next action is easily accessible and the main view will show me only one next action for each list and will show me the next one when I complete the current. That's great. However, lists are not cheap. As in, I need to pay to get more than 5, and it costs more than RTM. I did not feel that I can create them willy nilly, which meant I felt confined. Nice app, and an integration with evernote that I will never use, even though I am an evernote user. Better luck next time.

Conclusion

I've returned to Remember The Milk. I should focus on doing, more than what to be doing.

Freelance Freedom #213: Getting Things Done


Labels:

Comments

Pekka Klärck said…
Did you try the following Android app as a front end for Todo.txt? Looks handy and isn't overly expensive.

http://www.appbrain.com/app/todo-txt-touch/com.todotxt.todotxttouch
3:09 AM
Calvin Spealman said…
Pekka,

yes, that is the todo.txt android app i was referring to.
6:38 AM
Dustin Lacewell said…
http://orgmode.org/
11:23 PM
Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro...
4 comments
Read more