Somewhere around just 20% of people do pair programming. It seems to be an incredibly effective technique, according to people who follow it. I go over some of those reasons and micro case studies of organizations having success with pair programming. It seems like the right thing to do.
- My Pairing column from October at The Register — The comments section is especially good for common sentiment about pair programming.
- Charles Lowell — We used to do a podcast.
- Gartner survey on pair programming adoption — I got the number wrong: it's actually around 20%, not just 10%.
- Mark Ardito goes over HCSC’s astonishing success with pair programming — They thought it'd take 12-15 weeks to get their MVP done, but it actually took 5.5 to 6 weeks we finish.
- Selecting people for pair programming and their enthusiastic response — More from Mark Ardito on HCSC's adoption of pair programming.
- Phil Horowitz talks about how exhausting pairing is at first — At Perforce: "This makes pair programming intense, especially at the beginning. At the end of the first day, I couldn't go home. Before I could face humans again, I put my phone on airplane mode, ignored my usual online accounts, and went to the gym for two hours of self-imposed isolation."