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


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
Calvin Spealman said…
Pekka,

yes, that is the todo.txt android app i was referring to.
Dustin Lacewell said…
http://orgmode.org/

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

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 operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…