The '@todo' identifier states one thing clearly:  The following information is what's left or what's next to do.  It can be compared to the @NextAction context in GTD.  Once that action is completed, there may be another one next and subsequently a '@todo' identifier with that information will be listed.  The difference between that and GTD is that it's left in the code.  But, with a good IDE or a simple awk command, you can compile the list of @todo's for a project thus returning it to a GTD like state.

I'm the kind of person who's insane attention to detail will leave me always uncovering a rock or looking at a problem from all perspectives.  Some people call this being a pefectionist.  One of the major problems with being a perefectionist is that they will refine and tweak themselves into never getting anything done.  Analysis through paralysis is a common phrase for the problem.   And yes, I have that problem.

As some of you may know, a couple of years ago I hit rock bottom in paralysis and have somehow climbed my way step by step by implementing the GTD mehtod (as well as making other life changes).  The perfectionist in me still lives.  The initial mind dump and inbox organization took me about 3 days.  One of the hardest things to do while implementing the methodology was not being sure I was doing it right.  The common voice of the perfectionist.

So I'm slowly learning ot become an almost-perfectionist.  I still do my tweaks and twinges, but set a time limit before sending the product off.  Whenever I do so, there's that voice that doubts whether or not I've done right.  Even when I use a time limit, it reaches out and pulls me down to make sure I double check and triple check everything.  It's going to be with me forever.

Last month, an 'ah-ha' moment came.  And no I'm not talking about jumping up and singing 'Take on Me.'   What I'm talking about is when I started brushing up on PHPDoc, I realized that the '@todo' was the trademark for the perfectionist.  I can roll some code out but appease the perefectionist in me with the simple 5 letter incantonation.  The code is out and I can always come back to it to tweak and twinge.

I've accepted the fact that I will never be happy with my work.  I've also accepted that I will always find something wrong with it and attempt to fix it on the spot.  But with the '@todo' action I can drop the noted fix and move on.  I feel much more relieved and am producing more now that I've left @todo's not only in my code, but also in my other projects, my friends, my family, and my life.

Needless to say, the holidays brought me some changes this year on both the personal and professional side.  A couple of years ago I implemented the Getting Things Done (GTD) methodology to help account for changes in my life and to influence the direction it was going.  I recently had the opportunity to start a fresh GTD setup at the office.  Here are the steps:

1. Download Thunderbird 3 Beta 1



2. Setup the mail account.  Mine was an IMAP implementation so access to it via a webmail interface was kept in place.



3. Download and install Lightning Daily Updater.  The current stable version is for Thunderbird version 2.  This Add On for Thunderbird grabs the nightly, version 3 compatible calendar extension.
4. Be sure to enable the Google Calendar Provider in the options for the updater.  This was used to sync up office specific events to my main Google Calendar.



5. Run the updater and install both Lightning and the GCal provider



6. Add 3 local calendars for the main GTD contexts: @NextActions, @SomedayMaybe, @WaitingFor
7. Setup main calendar to sync with external Google calendar, using the private XML url from your calendar's settings.



8. Setup the projects context as Categories in the Lightning Preferences

This is a little bit different than what I had before.  I'm taking the calendar/task approach much differently.  Before I used Horde's implementation of their organizational modules to manage an action and an action that was time sensitive.  With Thunderbird and Lightning, the idea of a task is strongly coupled with a calendar item.  So I had to create the separate local calendars to give a place for tasks to land.  This turns out great because now I can create new contexts in the future as separate calendar types.

So far the implementation is going well.  I more times than not funnel all tasks Thunderbird's way but have caught myself once or twice avoiding the email client.  The next step for me is to explore what the benefit for me in syncrhonizing this setup with my Gmail/RememeberTheMilk system for my main GTD implementation.  It's still a little early, but if I feel the need to jump ship, I'll let you know.

Update 6/5/09: Changed the download link for Thunderbid beta.