--

I do not intend this post as a normative case for pair programming. I'm just trying to summarize research around the area and inform the reader of pros and cons. The decision of whether or not to use it is totally up to teams and individual developers - I fully agree. But at least, those decisions should be informed by facts as much as possible, which is what I try to provide here.

At the same time, I'm a very solo-oriented developer myself. And I recognize there is a pitfall there as it can blind me to issues that others can see. I've found value in pairing myself, even if that required some nudging by others. But thats just a personal take on this post.

--

--

Christiaan Verwijs
Christiaan Verwijs

Written by Christiaan Verwijs

I liberate teams & organizations from de-humanizing, ineffective ways of organizing work. Developer, organizational psychologist, scientist, and Scrum Master.

No responses yet