In other plain text GTD systems, a task might be a line in a list contained in a text file. In Things, each of my tasks was an item in a database that also had separate fields for tags, notes, and a due date. The core principle of my GTD system is this: every task gets its own plain text file, whose filename is the name of the action I need to take. But this does allow me to replicate the way I was using Things, with some added advantages I didn’t even know I was missing. I should stress that I do not claim that this system fully replaces the functionality of Things, which remains a good piece of software.
That’s when I started developing the following system. I was also reluctant to shell out at least another $20 for the iPad version.
NOTATIONAL VELOCITY FOR MAC CODE
I began thinking about alternatives to Things, though, when I got an iPod Touch, and then an iPad, and joined the legions of Cultured Code followers waiting longingly for cloud synchronization (which is now apparently coming soon). I used it much like Shawn Blanc used to and Ryan Cordell does, so if you’re not familiar with the program, start there. Even today, I still think Things is a great program. When version 1.0 appeared and quickly began winning awards, I gladly shelled out the asking price.
I got hooked on Things when it was still in free beta. I started using Things at the same time I was introduced to GTD, in the Spring of 2008. This post does just what its title says, so if terms like GTD, Things, and Notational Velocity mean nothing to you, you may want to move along: there’s nothing to see here but an excruciating display of plain-text nerdiness.īut if you are looking for a way to implement the Getting Things Done approach to task-management on your computer without spending much (or any) money, if you are a devoted user of Things by Cultured Code who has begun to toy with alternatives that support cloud synchronization, and/or if you secretly thrill to posts like this one, read on.
0 kommentar(er)
