Caveats: It was designed to work with this year’s OASIS, it discards some data, it may be full of bugs, etc. It was hacked out in less than an hour until it did its job sufficiently well, then left as it was.

That said, it worked great for me. Also, it puts all posters from a given session in the event description of a single session item. Here it is:


#!/usr/bin/env perl

foreach my $key ( keys %psessions ){
my $sep = '","';
print '"';
foreach my $subkey (@subkeys){
print $psessions{$key}{$subkey}.$sep;
}
print $psessions{$key}{'location'}.'"'."\n";
}


I printed this shot glass, and then drank some whiskey from it to celebrate! To success!

You eventually learn that true priorities are like arms; if you think you have more than a couple, you’re either lying or crazy.

–hotdogsladies

Astute as that is, how does it help you choose what to do when you sit down at your desk? Sure, there are the obvious things. But if one of your priorities is “start a company”, and another is “maintain my relationships with my wife and daughter”, there’s still a lot of ambiguity when deciding just what is the best thing to do next.

I’ve discovered that keeping an ordered list of goals (note, my actions are not ordered or “prioritized”) helps immensely. It has two main benefits:

1. When considering adding a new next action, project, commitment, or whatever, it’s easy to look at or think about the list and say, “This does [not] match up with any of my goals. I will [not] incorporate it into my to-do list.
2. When sitting down to plan your day (you do that, right?), it makes it easy to decide what goes on the list. Start at the top of the list of prioritized goals, and work down. Pick actions suitable to your energy level, setting, etc, that move you toward your most important goals first.

Of course, you can’t really assign priorities to your goals. They exist. You just have to think about them and then formalize them by writing them down. More wisdom from Merlin:

I think priorities are simple to understand precisely because their influence is so staggeringly clear and unavoidable to behold, then act upon. Ready for this one?

A priority is observed, not manufactured or assigned. Otherwise, it’s necessarily not a priority. [Emphasis his]
…
In my book, a priority is not simply a good idea; it’s a condition of reality that, when observed, causes you to reject every other thing in the universe – real, imagined, or prospective – in order to ensure that things related to the priority stay alive.
…
Example. When my daughter falls down and screams, I don’t ask her to wait while I grab a list to determine which of seven notional levels of “priority” I should assign to her need for instantaneous care and affection. Everything stops, and she gets taken care of. Conversely – and this is really the important part – everything else in the universe can wait.

–Merlin on 43Folders (The entire post is definitely worth your time and a major part of the inspiration for what I’m writing here.)

Here’s the exercise to do for coming up with your ordered list of goals: think about what’s important to you in life. Really important. Everything-stops-for-it-important. Write it all down. Compare the items in your mind — if you had to choose between two of them, which one would come first? Repeat until they’re in order.

See, it’s insightful for Merlin to talk about how priority just happens, but it’s so easy to forget about what’s important to you when you’re sitting in front of a computer (or a blank canvas or staff sheet, or whatever). If you want a method to ensure that you stick to what’s really important to you when distractions abound, give it a try.

I’ll give you a real-life example of how this was useful for my wife Amanda and I. Between our jobs, our daughter, and her day care, we have very little time or money to spare these days. We were making a list of goals using the method I described above, and I said, “maybe we should pause Netflix for a while.” She said something about how we enjoy watching stuff from Netflix and we have so many interesting things queued up to watch. I thought for a second or two, and looked at the list of goals that we had so far made. I asked, “Where on that ranked list of things that are important to us does ‘sitting together not interacting and watching tv shows and movies’ fit?”. She replied: “pause it”.

What are you still doing that wouldn’t make it onto your list? What aren’t you doing that would?

The guy I’m talking about is Tim Ferriss. He wrote a blog post a little while back called “From Geek to Freak: How I Gained 34 lbs. of Muscle in 4 Weeks”. I found that post at a time when I’d been struggling to figure out how to weight train correctly. I thought surely there must be some good scientific information on weight training, but what I found online (I later found a pretty good book) was a massive mish-mash of pseudoscience and mythology.

What I wanted was to build some muscle mass to improve my strength and appearance. The only thing that’s ever worked for me before for that purpose was lap swimming, and it took a ton of time and a nearby pool. I have neither of those now, so I decided to give Tim’s technique of lifting large weights for only a few reps a try. It promised significant improvement in only about 30 minutes per workout, twice per week. I was skeptical, and my wife was doubly skeptical.

To avoid as much bias as I could, I logged my progress in a Google Spreadsheet and published it here. I logged other observations on Think, Try, Learn’s new “Edison” platform, also publicly visible: Attempting the “Geek to Freak” muscle building technique.

The short version: it worked splendidly! Both my wife and I were pleasantly surprised at the results.

Long version:

It was very important to keep my protein and overall calorie intake up to the level I was burning. Using whey protein I maxed out my safe weight training protein allowance every day, and I used FatSecret.com to track all of my nutrition (which I do when losing weight anyway). I noticed that whenever I didn’t eat enough calories I stalled out pretty badly. If I hadn’t been tracking my nutrition and my lifting stats I probably would have been mystified as to the reason for my trouble, or just frustrated that I wasn’t making progress. I’ve had that problem before, and realized in retrospect that I was able to gain muscle well while swimming because I was eating things like two steaks or an entire wok of home-made General Tso’s Chicken every night for dinner. (Sort of a ‘duh’ thing now, right?)

At first I was trying to both lose fat and gain muscle at the same time. That worked for a week or two, but then I quickly stalled out on the muscle gain. I read a bit about this and it seems that when you first start a weight training regimen, there’s a ‘honeymoon’ period where your untrained muscles grow to meet the new load. After that period, I had to give up on losing fat simultaneously. However, now that I’m taking a break I’m finding it’s easier to lose weight as my increased muscle mass burns more calories per day even at rest. (I injured my leg stepping over a baby gate and then had to travel a bit. I’m planning on getting back to the weight training soon.)

I tried another one of Tims’ ‘hacks’ to improve my reading speed and found less dramatic results. His metrics for that technique are biased in favor of finding an improvement, even if there isn’t really one. I also logged my results carefully there and abandoned the technique after a few trials.

In the end, the Think, Try, Learn treat-everything-as-an-experiment approach worked well for me in vetting suggested lifehacks. I’m going to continue using both the weight training technique when I want to gain muscle, and the TTL experiment approach for trying new things.

Have you tried any experiments like this?

Matt’s been testing and honing his ideas on daily planning as an addition to a GTD-like system, and I recently had the pleasure of reviewing the results: his new eBook on daily planning, Where the !@#% did my day go?.

Despite having practiced daily planning paired with GTD for almost two years (and GTD for nearly four), I found several new gems in the book. In particular, the practice of inserting everything into the daily plan, including calendar and inbox-checking tasks, is new to me and will help streamline my current process. I opted to skip the ‘getting started’ phase of the book and the one-week challenge, given my experience, but I found that they really covered the nuances of the practice well. Furthermore, every pitfall that I’ve encountered in daily planning was addressed by Matt later in the book.

Matt also detailed a number of experiments to try, to help hone the system for one’s individual needs. These covered every single experiment and metric I’ve run on my daily planning, and added several more that I’m considering trying. Ultimately he suggests trying for a “touchdown” — finishing all of the tasks on the list. This is the rule for me, rather than the exception. It provides a really nice feeling of satisfaction at the end of the day, a feeling I couldn’t get from looking at my list of remaining, actionable tasks in PHPMyGTD (20-80 normally, I prefer to keep it below 40).

I found very little to criticize in the book, and most of it can be traced back to personal preference. For instance, Matt mentioned the use of an accountability partner for holding to one’s daily plans. For me this makes a massive difference in my discipline, enough that I created DidYouDo.it, a site for finding accountability partners. (It’s unfortunately not really active at the moment.) I also find it really helpful to estimate the time required for each task explicitly and then write it down, reporting back to my accountability partner each day how the actual times matched up to the estimates. On the whole, however, the book is nothing short of an excellent introduction and manual for daily planning practice. If only this book had been in my hands two years ago when I started this practice, I could have saved myself months of tinkering and lost time.

As a result of some conversation in the comments of another of Matthew’s posts, I decided to get a domain and start up a simple site (didyoudo.it) for finding accountability partners. It took a little finagling to get an Italian domain name, but I owe one of my fellow graduate students a case of beer for the effort he undertook to get the domain for me. It seems you must be a European citizen to get an Italian domain name, and they require arcane things like faxing signed forms and so on. I think the name has a nice ring to it.

So far the site hasn’t really gotten much traffic. One guy found it via my Tweets on the subject and we just started the accountability partner thing today (yay!), so in a sense it’s been a successful venture. On the other hand, I had grander visions for the site. I wonder if I should broaden the focus a bit from productivity-related accountability partners to any accountability partners? There’s a major Christian accountability scene, and I didn’t really want them to dominate the board, but maybe it’s not worth worrying about.

Have you ever thought about working with an accountability partner? If you want to, and you feel like you’ve got a good grasp on your productivity otherwise, come post something at didyoudo.it. If you want a little more coaching, I understand that Matthew does a telecoaching series on daily planning and accountability. It might help get you off to a good start before you find your own accountability partner.

Of course, I could die in a car accident any day, but we have to think of these things practically and probabilistically.

The script runs in Bash — you’ll need a Mac or Linux machine, or Cygwin on Windows I suppose, in order to run it. I have it running on my webserver and emailing me each morning via a cron job. The math should be pretty self-explanatory, and you could easily add your own metrics. Note that I’ve changed my exact birth date for the posted script here, since in some situations that could be considered confidential information.

The estimated death date I got using the “Normal” mode of the Death Clock.


#!/bin/bash
# Prep
# YYYYMMDD
BIRTHDATE="19820301"
DEATHDATE="20570127"
DAYSPERYEAR="365"
SECONDSPERDAY=$((24*60*60))
SECONDSLEFT=$((`date -d $DEATHDATE "+%s"`-`date "+%s"`))
SECONDSTOTAL=$((`date -d $DEATHDATE "+%s"`-`date -d $BIRTHDATE "+%s"`))
# There's probably a nicer way to format the percentage but this works
PCTOVER=`echo "scale=2; (($SECONDSTOTAL - $SECONDSLEFT) / $SECONDSTOTAL)*100" | bc | sed "s/\.00//"`
DAYSLEFT=$(($SECONDSLEFT / $SECONDSPERDAY))
YEARSLEFT=$(($DAYSLEFT / $DAYSPERYEAR))
# Output
echo "Percent Over: $PCTOVER"
echo "Days Left: $DAYSLEFT"
echo "Years Left: $YEARSLEFT"


The output looks like this (the numbers are made up):

Percent Over: 29
Days Left: 19002
Years Left: 51


I do hope and think it reasonably likely that Ray Kurzweil is right, and that my life could be substantially extended, but I’m not counting on it, and I don’t think I should — it would kind of defeat the purpose here. Read the letter by Seneca in Tim Ferriss’ post to see what I mean.

Suggestions for improvements to the script are welcome.

NB: This doesn’t work on OS X, because the date command is different.

I’m getting back on the horse.

Anyway, it’s a little tricky to apply the Martini Method when using LaTeX — as a markup language a bit like HTML, it’s full of special words, symbols, characters and whatnot that are not actually part of what you’re writing. A simple Emacs word count will not do the trick. Much as I’d love to count all of those extra words, the point here is to produce a certain volume of output and that would miss the point. Plus, it’s dishonest. There exists a PERL script that will parse LaTeX and count the non-special words. However, someone’s gone even a step further and made a nice web interface for it, with color coding and everything. That interface is here, apparently hosted by one Einar Andreas Rødland in Norway.

So far, it’s working quite well for me. Unfortunately, it just informed me that I’m not quite to my desired word count yet. More writing!