Two heads are better than one, especially when it comes to large, mission-critical software projects. Whether you’re just starting out as a developer or curious about pair programming, Jason Garber’s hands-on guide takes the mystery out of effective pairing. You’ll learn what good pair programming looks like, how to be a better pairing partner, and how to explain the benefits of pair programming to skeptics at your organization. Walk into your next pairing session confident and prepared for the adventure ahead.
I hadn't strong feelings about pair programming before, but this book provides a very good mindset and advices about how, when and why to use it. It is short so takes only a few hours to read, however, has a big density of value per sentence
Good introduction of Pair Programming, in particular the focus on the social side (feedback and conflict resolution) that one must pay attention. Also, it reminded me of how much we derailed from Extreme Programming and how we need to recover it.
On the downside, it lacks a description of specific practical aspects, such as: - basic concept of driver and navigator - does the driver only types what the navigator says? - examples of different setups real live people have done with this - etiquette for Pair Programming - patterns and anti-patterns - a more methodological way to start introducing pair-programming in your team (e.g. trying 30min every Friday seems short, but maybe in some organizations that's the best we can do to start)
Interestingly, while lacking in the text, the last chapter on Resources lists a whole lot of references (sites, book, etc.) that address some of the shortcomings of the book, having sections named "Pair Rotation" and "Managing resistance and anti-patterns". I feel some of this content should have been reflected in the book.
In summary, it's a good starting point that leaves us wanting to explore more sources on the topic.
The practical parts of the book where very good. I'd like even more of those. Maybe even some examples of good ways to do it and bad ways. The technical parts already feels dated even though i read the book same week as the preordered copy landed in the mail. The author says multiple times that he prefer Zoom when remote pair programming but never mentions why.
But i really recommend it for anyone curious about pairing. A fast read and a bunch of learnings even though i'm familiar with the subject.
Very succinct intro to the practice of pair programming. If you're a beginner and want to know some tips on how to best introduce that on your team, then this is a great read.