The SquizLog

Pair Programming Intensity

Daniel Bradby has posted some interesting thoughts based on his experiences of Pair Programming.

In particular he talks about the intensity of pairing and how it is at odds with the "flow" state one experiences when immersed in programming alone:

I have found it difficult to get into any sort of flow while pairing. In fact I find myself on the edge of flow, constantly trying to enter that flow state to "just code", while having to stay outside of flow so as to be able to communicate with my partner. I think this accounts for a good portion of why I feel pairing is so intense and tiring. Maintaining that semi-flow state wears me down.

These words struck a chord with me. Pair Programming is undoubtedly intense and tiring. In my experience it has also been less satisfying.

I think Daniel has highlighted one of the reasons, for me anyway. Pair Programming doesn't provide individual programmers with the opportunity to be immersed in a programming experience that may lead to a personally satisfying outcome.

In my humble opinion there must be a better way to achieve some of the benefits of pair programming in a slightly modified form. For example, pair reviewing code rather than the navigator reviewing it whilst it is being typed.

As you can probably tell, I'm not a fan of pair programming. I think it is useful in some situations, can work well with a well-matched pair but in general I have found that it doesn't work for me. Nevertheless, Daniel's post offers some helpful advice based on real experience.

Posted to Peopleware, Software Development by Keith Pitty