03 Mar 2013

A Week with ThinkingRock GTD

[caption id=“attachment_529” align=“alignright” width=“300”] By: Thomas van de Weerd[/caption]

The Good

My first week with ThinkingRock has gone REALLY well for adding tasks. I sit at the computer for much of the day and when a GTD task comes to mind I dump it via Cmd-Space GTD "description of task".

The Bad

Having a very efficient system for adding tasks paired with a HORRIBLY inefficient method of processing tasks causes my GTD Inbox to overflow.It’s like having a firehose flowing at full strength and routing it into a gardenhose.

The Analysis

The method that I’m using for adding tasks is very well optimized and uses a decoupled system. Being able to send emails from any device and having the subject and content dropped into ThinkingRock as a pending task is GREAT. When I go to sort the tasks, I’m stuck with a system that very literally follows GTD principles, but doesn’t have sufficient keyboard shortcuts. Processing 35 items by tabbing through textboxes and radio boxes isn’t my idea of an efficient system. It also makes me wonder if other people are painstakingly mousing through the interface.

The Answer

Dig into the source files for ThinkingRock and add enough keyboard shortcuts to “get things done”. I started this yesterday on the plane to California and I’ll post back when I have a chance to work on it more. Given that I don’t know any Java (other than a session at the LeanDog CodeRetreat with Steve), this will be an interesting challenge :).

20 Feb 2013

ThinkingRock GTD: Torn Apart


Why am I engaging in this hipster habit of using Covey’s ‘Getting Things Done’ methodology? Because there’s something very valuable to it!

The analogies that Stephen Covey uses in his book hit home for geeks. He describes the working memory we humans possess as Random Access Memory, which requires energy to sustain it. Furthermore, he reminds the reader that if the RAM is busy, other thoughts can’t percolate through that stage of consciousness?

Sound too esoteric?

Let’s get down to bare metal. Or brass tacks. Or any other colloquialism that suits.

Throughout the day I have ideas. Many of them are good ideas :). Many of these good ideas percolate to the surface at inopportune moments… like meetings, reviewing reports, or writing code. These ideas are GREAT but what’s their value if they disappear before I can act on them?

Nothing. That’s how much value these ideas have if they flit right back out of my consciousness. Might not be a big deal if it’s remembering a food item to pick-up on the way home. Might be a huge deal if it’s a programming or business idea that could be implemented and turned into a product!

What’s the solution?

I mentioned using ThinkingRock GTD system in this post. ThinkingRock v2.1 is an open-source project hosted on SourceForge.

ThinkingRock does the usual stuff that one would expect from a GTD program: * Collect Thoughts in an Inbox * Processing * Organization * Reviewing * Action

What’s the killer feature of this app for my workflow?

That ideas can be dumped into it using the universal communication currency of our age, EMAIL!

My goal is to reduce the friction in the GTD system so that I waste as little energy as possible on the process itself.

Email input is a very powerful feature. I’ve setup a dedicated email account for receiving GTD tasks and then configured ThinkingRock to import tasks from there every 15 minutes.

The next step in this process was writing a short commandline script that is prefilled with the GTD email address. The script combines all commandline input less the scriptname itself and uses that value as the subject line of the email. This makes for an incredibly fluid system of GTD task entry.

Here’s the simple Ruby script for this task (note that auth info is placed in ~/.gmailrc):

But wait, there’s more! If you keep reading this blog post, you’ll receive more time saving advice at no additional cost. That’s “#{SOME_MADE_UP_VALUE}“!

Back to the point, I integrated this script into Alfred.app. Now the tasks can be entered directly from Alfred!

I’ve only scratched the surface so far with getting back into the GTD methodology… but I’m excited! Having better programming chops this time when approaching GTD is certainly improving the process :).

Still to come:

I discussed in this post that I wanted to use the open-source version rather than the newer closed source version because of having the ability to dig into the code. In an upcoming post I’ll discuss how the open-source program allowed me to investigate the data structure used for ThinkingRock in a way that would be much more challenging if I lacked access to the project source-code!

Let me know in the comments or on Twitter (@_ZPH) if you have ideas on how to improve the process.