In the GTD system, you plan in
projects. A project is just a grouping of actions with one goal ("Fix bug in
pdf generation"). So planning in projects, but you do actions in a
context. "Google for obscure pdf error message" in the
context. "Brainstorm with colleague' in the
One problem many programmers have: 80% is
That's actually OK for me. Those contexts are especially useful for the other
20% of the cases. If I go to the city center, a quick look at the
context gives me a shopping list.
@zest shows things I really only can do
while I'm at the office (Zest software).
A nice possibility of omnifocus is to nest your contexts. Some ideas on how to use that:
@computer? Most will still go in there, but I've added a sub-category
offlinefor when I have tasks that I'll probably handle when I'm offline (which means in the train). And
ubuntufor when I'm near my wife's home computer.
@cityhas a few stores I often visit as sub-contexts. Not that I use them always (the shopping list for food is a note on the fridge in the kitchen), but it comes in handy when printing the list for offline in-city use :-)
with toolssub-context of
@homeunearths some small tasks that I can get off my plate quickly now that I have those tools in my hand.
See also my first entry on how I use omnifocus
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):