Getting Things Done with Tracks

Doing something for the first time is always an educational experience. Koz and I are just about ready with the first installment of The Rails Way, and in preparing it we learned a few things.

Most significantly, we learned that multiple short articles are preferable to one lengthy article.

With that nugget of wisdom in mind, tomorrow we will unleash the first in a series of four articles reviewing the GTD application Tracks. Luke Melia’s submission was one of about a dozen that we recieved—quite a few more than we expected for this first run of The Rails Way!

We were drawn right away to the Tracks submission for a few reasons. First, Koz had used it before and was somewhat familiar with it. Second, upon perusing the code, it illustrated a few common errors and antipatterns that we thought would be helpful to address in this first series of posts.

Note that we are not “picking on� Tracks here. The issues we will address are definitely not unique to Tracks. Koz and I have both seen them in numerous other projects, which is why we’re talking about them.

We extend our thanks to Luke and to everyone else who sent us code, for their faith in us and in this blog. We’ve been quite overwhelmed by the positive response to our original announcement: two weeks and zero content later, and there are already nearly a thousand subscribers to the RSS feed! We hope this series and the many series to come will prove that faith to be well-founded.

So, brace yourselves! Koz will be posting the first of the articles reviewing Tracks in just a few hours.