Millarian

Recently, my employer, Integrum Technologies, has allowed me to work from home one day a week. This is due to rising gasoline prices combined with my distance from work. It’s great for me as I’ll save quite a bit of money each week as well as reduce my overall emissions. However, this has presented us with a slight dilemma: how do we remote pair effectively?

Pair Programming

Integrum subscribes to a variety of Agile practices. Perhaps the most prominent is working in pairs, a.k.a pair programming. I was first introduced to the idea of pair programming around 1999 when I was at the University of Arizona learning how to completing my BS. At that time we simply learned the theory from a professor, but didn’t actually try it.

About 16 months ago I was working in a contract position with my friend and phoenix Ruby on Rails developer, Josh. Toward the end of our time at that contract we attempted pairing and found it worked really well. When we were hired as contractors at Integrum we paired on a project form start to finish and then later, when we went full-time, we paired with the rest of the team members. These positive experiences with pair programming have convinced me of it’s usefulness.

Now that I work a day from home, how will I pair with my various teammates?

Remote Pairing

I’m sure there are many, many ways to pair remotely, but here I will describe our first attempts at pairing remotely. It may help that we’re an all Mac shop, but we found it rather easy to get up and running quickly.

Systems

At home and at work we are using iMacs running OS X 10.5.4. The built in iSight and microphone are great for what we need right now.

Complaint: Noise. It’s everywhere, seriously. The mic picks up everything.

iChat

Yep, that’s right, iChat – video chat specifically. We simply fire up our iChat instances using our Integrum Jabber IDs and request a video session. Seriously, that’s all we do. The sound and video quality have been more than adequate for pair programming 7 hours a day.

Our first attempt at this was flawless, well… until it just stopped working that is. After a little research we found that I probably needed to open the right ports to maintain a consistent connection (this post on iChat Routing Problems helped). After I did that we haven’t had a problem.

Complaint: Video chat over iChat can sometimes lag or have artifacts, especially during peak times. It’s good enough, but would be nice if it were smoother and clearer.

Screen Sharing

While we’re pairing we share the screen on one of the computers. When we’re done we turn it off. This allows us to both have control of the keyboard/mouse if we need it and has helped immensely in making us feel like we’re both working. We take turns driving while the other gives advice or comments and we can smoothly transition from one driver to the other.

Complaint: From my end the connection latency can sometimes hinder progress. If I hit one of the Exposé areas of the screen and all the windows separate it can almost bring rendering on my side to a halt. There also seems to be a problem with select via the mouse. When I click and drag to select some text the screen jumps to the top or bottom immediately, selecting all text between. I’ve had to get better with the keyboard.

iSight + built-in microphone + iChat + Screen Sharing = Adequate Pairing

I do have some complaints about the current setup, but I’m willing to keep going until we find better solutions. Perhaps we should try using Xbox Live as I’ve heard some people suggest.

I think the next steps are to secure some good microphone headsets that will reduce the noise and allow us to hear one another more clearly. Then we can look at replacing iChat and Screen Sharing.

As tools for remote pairing progress I can see more developers turning to this as a solution to save money and time while still retaining their communication with their team, especially with their pair. Pairing remotely can reduce cost for the developer and the company, save time and reduce emissions because the developer no longer commutes. And if their whole company is remote then all the better!

The folks at Integrum recently had a discussion about avoiding distractions while pair programming. We all know how many distractions there are in today’s world, everything from email to blogs to Twitter. It’s hard to not get distracted by all of these things, as they have become so prevalent in our lives. We want to be in the know and there are many tools out there that let us do just that. They constantly run in the background or popup, they email us, they text message us, they demand our attention…

Look at me, I’m a tweet!!
No, I’m working.
But I’m a direct message from iJustine!
Well… okay, just this once!

But it’s not once, it’s all the time… constantly interrupting (seriously Justine, stop, I’m not going to respond). When someone is paying you for your time, they don’t want to be competing with all these distractions.

So what’s appropriate etiquette for a person working in a pair programming environment? I asked my 4 year old over dinner to see what he thought.

The Interview

me. Do you know what it means to work in a pair?
ethan. When 2 people are working together.

me. Good. What about focus? Do you know what that means?
ethan. Stay on track. Concentrate. Keep an eye on what you’re doing.

me. How about respect, do you know what that means?
ethan. Be nice?

me. Okay good, let’s get started.

me. When you’re working with someone as a pair is it okay to check your email, instant messenger or twitter?
ethan. No.
me. Why is it not okay?
ethan. Cause we might lose focus.

me. If we were working together and I was having trouble solving a problem, how could you help me?
ethan. I could tell you how to do it.
me. What if you didn’t know how to do it?
ethan. We could think of an idea and do it.
me. Should we think by ourselves?
ethan. No we should talk and hear… and choose what we want to do.

me. If were working together and I get distracted, what should you do?
ethan. Daddy, what are you doing? Please pay attention. You made me distracted and I don’t know what I was working on.

Conclusion

This interview proves beyond a doubt that my 4 year old knows what it takes to work in a pair programming environment. He was polite, but forceful in his remonstration of my lack of focus. His answers were not overly complex, he kept it simple. Which is as it should be since it really isn’t all that complex – there’s a reason the acronym KISS exists.

So there you have it, think like a 4 year old and you’ll do just fine in any pair programming environment :)