I’m an Independent Consultant

October 20th, 2009

I’ve jumped.

After 7 years of ThoughtWorks, 2 years of Pivotal, and a couple of small contracts in between, I’ve gone independent. I’m looking for work as a coach, trainer, or facilitator – mostly focusing on software teams that want to work on their process. So, not very far from what I was doing – I expect engagements will be a good deal shorter and won’t be doing any more straight development work.

A lot of work

I really thought I’d have more free time. In fact, between the gigs I’ve been fortunate enough to land, finding and preparing talks to give,, meeting people at networking events, reading everything I can get my hands on, and writing on my blog, my website, and about facilitation patterns, I’ve got more on my plate than I could ever actually do. Nevermind the non-profit I serve or the dance classes I teach. If it wasn’t for GTD, I’d never see my wife or friends.

Still, this is way more fun than I’ve had at work in a while. I seem to be getting the most important and strategic things done, and my wife has been giving me a ton of support. I’m also getting better at saying “no”, thank God.

Finding work

I’m not sure I can claim to have a fully developed marketing “campaign” yet, but I’m getting there. I’m reading and working through Book Yourself Solid, a book that has been three times recommended to me. It’s good.

My current strategy is to play to my strengths. I’ve got a lot of targeted experience and knowledge about enabling agile teams. Face-to-face, I’m a good listener, a decent connector, and gosh darn it, people like me. I’m trying to put myself in front of as many people as I can and be excellent. So I’ve been giving talks and leading exercises at conferences and user groups. I’m also focusing on establishing deep connections with people. I want to find your pain and help you with it. Maybe that means connecting you with someone else, suggesting a book, giving you some free advice, just listening, or talking about how I could help you in a professional capacity.

So far, it’s working well. I’ve gotten a few leads and a bit of work, and I get to spend my time helping people from a place of integrity – not what I thought marketing would feel like.

What I need from you

If you’ve worked with me in the past, you now know I’m available, so keep me in mind next time you hear about a team that’s struggling. I’m also looking to collect some quotes about how awesome I am, so send those my way :).

I’m in the business of helping and connecting people right now. Let me know what’s blocking you, maybe I can help.

Array.to_hash() in Ruby

August 4th, 2009

I often find myself wanting this method. This is my 3rd or 4th writing of it – it’s shorter this time. Inject is my new best friend.

class Array
  def to_hash
    inject({}) {|hash, i| hash[i[0]] = i[1]; hash}

What this snippet does is take an array and turn it into a hash, like so

[["apple", 1], ["banana", 2], ["citrus", [3,4,5]] => 
    {"apple" => 1, "banana" => 2, "citrus" => [3,4,5]}

If I didn’t have to deal with the case where there may be subarrays, I’d use nick’s approach


My solution isn’t that much more code, and handles the case of subarrays.


Ola makes the good point that this is actually the best of both worlds :


Thanks Ola. …I still think inject is cool, though :).

Cards 0.9 is away

March 5th, 2009

Cards is a ruby gem that allows you to quickly capture a card wall into a spreadsheet then print it up using omnigraffle or export it to csv (or now tracker)

This release adds a couple really cool improvements in it :

1. Numbers ‘09 finally has applescript support, so Cards can finally reach into it and grab what it needs instead of requiring a csv export.

2. Pivotal Tracker now has a sweet RESTful api that we can use to throw stuff directly into it.

Wouldn’t it be cool if the next thing cards could do for you is update your spreadsheet to add the tracker ids for created stories? Then you could maintain the spreadsheet and tracker. Maybe even get 2 way syncing going or something…

To illustrate, Cards lets you take this spreadsheet from Numbers and turn it into the card walls in omnigraffle that created it.

[img:3330719206, small]




Running a Community Meeting for Burn Blue

March 5th, 2009

So first, some background.

In May 2007, a few of us started a not for profit in Seattle to promote blues dancing. We called it Burn Blue. It was my first take at helping to shape not just a team, not just a project, but a whole company. It’s been fun and a huge learning experience for me.

Burn Blue runs a weekly blues dance in Seattle. As such its success or failure completely depends on the dance community in Seattle that come to it. We’ve been really successful in reaching out to this community, and Burn Blue has done really well because of it.

I’ve personally had a lot of fun guiding Burn Blue toward being more community driven & transparent. I love this fuzzy stuff.

Fast forward to last weekend. I was running Burn Blue’s community meeting. We had promised people pancakes and a voice in Burn Blue’s future, and 35 people showed up.

There were however, a lot of challenges :
1. It was a lot of people, a lot of new people, people that hadn’t necessarily been to a community meeting before, people that didn’t necessarily know what Burn Blue was about.
2. There was a lot of information that we as directors wanted to get across to them about changes that we had made.
3. We wanted the people there to feel that this was THEIR meeting, that Burn Blue was there for THEM, and not the other way around.
4. We didn’t know what we didn’t know. We wanted to make sure that we discovered any other important things that needed to be addressed.
4. We wanted to actually get stuff done. We wanted actionable items out of the meeting along with the names of people who would do them.
5. We only had 3 hours.

Long story short, we did it right.

The directors and officers (all 5 of us) had met previously and talked about what we wanted to put into the meeting. We set a very rough agenda and recorded a few things that we wanted to hit. More importantly, we practiced setting an agenda in that meeting and working through it.

We had a big [Visible Agenda] and wrote ours down on a huge post it. It looked something like this :

  • 1:00pm – arriving, eating pancakes
  • 1:30pm – where are we? (temperature & retrospective)
  • 2:00pm – burn blue structure
  • 2:15pm – going over people’s input
  • intermediate lesson
  • venue
  • improving feedback
  • security

Basically, people got there and milled around a bit while we helped -topher with pancakes (this was in our house). Around 1:30, when the pancakes still weren’t done, I called everyone’s attention together and gave them a couple jobs while they continued to eat and talk.

First, I wanted to get a group [Temperature]. I had written down Burn Blue’s 4 part mission on a giant post it and I drew a line to the right of each for part for people to judge us on.

Second, I had two more giant post its with the classic “keep” / “change” from retrospectives for people to add things to.

This was all information gathering, so I let the [Participants Write]. I also gave them an expectation that part of the meeting would last about half an hour.

Half an hour later, the formal part of the meeting started. We explained a little bit about what burn blue was. Then we started to go through what people had written down.

Karissa, my wife, who’s also a director, saw people beginning to get excited and start talking over each other, and she suggested a few [Ground Rules]. We as a group settled on [Use Gestures], [One Conversation], and [No Stories]. We also hadn’t actually set an end time for the meeting, so I asked people when they wanted to end. We decided that 4pm would make the most sense.

As we talked about the temperature sheet and the keep and change sheets, we wrote down things that we needed to talk about onto the [Visible Agenda]. We almost used it as a [Parking Lot] for everything until after we were done going through the input we’d gotten already.

And on it went. We found, as we’d hoped, that a lot of the things that we (the directors) had wanted to talk about were also concerns of the community. There were also several things that we hadn’t thought about.

We kept going. Our [Ground Rules] kept us focused. Pretty early on, I asked the group for the authority to play “Time Nazi” as we had close to 20 agenda items to go through and less than 2 hours left. When we went over 5 minutes on an item, I’d let people know, but some items were important enough to keep talking about, some weren’t.

We jumped around a bit on the agenda. Several times, the same person that brought up an agenda item conceded that it probably wasn’t as important as another one, and we went in roughly order of importance, crossing off agenda items as we covered them.

We ended up finishing the meeting at 4pm, deciding to leave the last few agenda items uncovered until the next meeting in a few months. As we had talked about each item, we had also been adding to another [Big Visible Chart], our [Action Items].

People left the meeting (though many stuck around to hang out) with a feeling of excitement and ownership. A feeling that things had just gotten better, that they had been heard and they had helped that to happen, knowing what their next actions were. The meeting was a total success.

For my part, I’ve been working a lot on http://facilitationpatterns.org/ lately and have had all these awesome patterns swimming around my mind. I called up several for this meeting. And had done so previously for the directors just before. This helped made the facilitation of the meeting into a joint effort.

It was really fun to take the reigns and pull out patterns that fit and customize them to the situation. I’m looking forward to our next meeting.


March 4th, 2009

I’ve been working on http://facilitationpatterns.org/ for a while now. I’m hoping that it will eventually become a book.

You should check it out if you’re interested in facilitation, and that includes running a meeting, a standup, a retrospective, a release planning session, a quickstart, or even just brainstorming holiday plans with your family.

I have ~ 50 patterns up there already, but most are not fleshed out beyond a short summary. Though expect more up there over the coming months. I’d love feedback on the patterns, the structure, or anything else.

What I’ve heard from veteran facilitators that I’ve shown it to so far is that it’s a really good reminder of a lot of what you already know. This is what I’m going for. However, I think even these veteran facilitators will find a few new things to add to their toolbox.


Stop running test:unit tests when using rspec

January 16th, 2009

You know those 3 lines that show up every time you do an rspec run?

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -Ilib:test "/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb"  
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -Ilib:test "/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb"  
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -Ilib:test "/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb"

…yeah, those lines. I hate those lines.

So let’s get rid of them!

Each of those lines is rails trying to run test:unit. RSpec replaces the default rake target by doing this:

task :default => :spec

BUT If you’ve played with rake before, you know that this doesn’t actually replace the default target, it only adds to it. We need to remove the default target then point it at :spec

Turns out that’s not too hard. Put this code (got it from here) at the end of your Rakefile:

Rake::TaskManager.class_eval do
  def remove_task(task_name)
task :default => :spec

You’re all set!

A New Blog, Git, & Capistrano

August 24th, 2008

I’ve had my fun with ruby.

I wanted to learn ruby, so I wrote myself a blog. Then, I wanted to learn rails, so I migrated it to rails. Then, the spam was too much, so I migrated to Typo. Then, I couldn’t take Typo’s memory footprint, so I moved to Mephisto.

But you know what? Even Mephisto is a pain to deploy, and is still a resource hog. It’s kind of the nature of ruby and rails apps. And what’s the benefit to justify the cost? Aren’t there other more mature, stable, better supported and more flexible blog engines in other languages?

…yes, there are like 50 of them.

So I’ve migrated yet again, this time to WordPress.

I’m really happy with it, but I did have some cool toys in my rails world that I didn’t want to give up. I can use my own machine as a staging environment to blog changes. I can also deploy with a simple “cap deploy”.


My entire website now lives on github and I use capistrano to deploy it after making edits locally. It looks something like this:

git commit -m "..."
git push
cap pull

And to give you an idea of the goodness that is ruby and cap, I also wrote a script to pull the databases on my server down to my staging environment. After all, what’s the point of staging if it uses different data. Using looks something like this:

cap backup
rake db:pull db:restore

If you want to see how this is done, check out repository

Making Line Up / Down not suck in Textmate

August 5th, 2008

I think I blew Steve Conover’s mind last week.

He, like me, and every other sane rational person I’ve ever met, thinks that when you say “line up” or “line down” in a text editor, it should take the line(s) you are currently on and move them up, in their entirety. Furthermore, that if you press “line up” 5 times, the line(s) you are currently on should move up 5 lines.

Textmate, as much as I love it, does not do this, and this has long been a source of contention and strife among my colleagues at Pivotal.

This, however, is a story with a happy ending. Last week, Steve and I were pairing on Textmate, and he was complaining that line up / down wasn’t working properly. A couple hours later, I had a brilliant insight. This is how you fix Textmate’s line up / down :

Pull up textmate and type :

command-control-up arrow

This will start recording a macro, select the current line, move the current line up, stop recording the macro, and then save the macro.

Next, name your macro “line up” in the dialog that just popped up, and give it a key equivalent of command-control-up arrow.

Congratulations, you just fixed line up!

Now let’s do the same with line down :

command-control-down arrow

This time, name it “line down”, and give it a key equivalent of command-control-down arrow.

You of course don’t have to do all this with keyboard shortcuts, but it’s really impressive if you do :)

Eventual Consistency, or things will all work out…eventually

August 5th, 2008

So we’re working with Amazon’s SimpleDB. It’s pretty sweet, though the ruby libraries for it are still a bit primitive. One of the problems you run up against when you’re writing integration tests against it is eventual consistency.

Take this test :

it "should save" do
  customer = Customer.create!(:name => 'bob', :email => [email protected]')
  customer = Customer.find(customer.key)
  customer.name.should == 'bob'

The way SimpleDB works, you’re assured that Customer.find will work…eventually, but not right away.

For a couple days we contented ourselves to just run the integration tests a couple times until they didn’t error out. But that got old.

Enter “eventually” :

it "should save" do
  customer = Customer.create!(:name => 'bob', :email => [email protected]')
  customer = eventually { Customer.find(customer.key) }
  customer.name.should == 'bob'

It’s a very simple method (below) that just retries the passed in block until it succeeds, timing out after 10 tries. Super simple, works like a charm. Thank you ruby.

Here’s the source :

def eventually(tries = 0, &block)
  raise if tries >= 10
  sleep 0.5
  eventually(tries + 1, &block)

I will say, I can’t help but smile every time I write “eventually” in a test… :)

Linking Delicious Library to Your Movies

July 25th, 2008

If you’re like me, you value traveling light. If you’re like me, anything that can live in digital form does. I haven’t seen most of the actual DVD’s I own for quite some time now. But the movies on them all live on a hard drive that’s hooked up to my television. I love the instant gratification. I love that I can download a movie to my laptop and watch it on the plane.

Delicious Library makes this even cooler. As much as I love having everything digital, I miss being able to take a quick glance at 100 covers and recognize the one I want. I miss the association between images and memories. Delicious gives this back to me.

However, it’d be really cool if I could go browsing in my delicious “library”, find the movie I want, and double click it to play. Turns out you can easily extend the program with applescript, and a couple hours after I decided such a script didn’t already exist on the interweb, it now does.

This applescript will open vlc with the file associated to a media object in delicious. If there isn’t one already, it will prompt you for this file and then remember it for next time. It’s really simple, and happy :)

-- this will play the currently selected file in vlc using either 
-- the associated url or prompting you to find the file on disk
tell first document of application "Delicious Library 2"
    set selectedMedia to selected media
    repeat with selectedMedium in selectedMedia
        set movieUrl to associated URL of selectedMedium
        if movieUrl starts with "file://" then
            set movieFile to rich text 8 through end of movieUrl
            set movieFile to (choose file with prompt "Find the file for " \
                                            & name of selectedMedium & ":")
            set associated URL of selectedMedium to "file://" & movieFile
        end if
        tell application "VLC"
            open movieFile
        end tell
    end repeat
end tell

– thanks Wes for pointing me to such a cool program!