Pair programming is an Extreme Programming practice of coding through interpersonal process. There are many ways to get it right and many more to do it wrong. This practical reference offers precious tips for pair coders with all levels of experience.
Among software engineers, pair programming occurs when two coders join together to write code together. It's an incredibly efficient and focused means of knowledge transfer. However, developers are also known for having prickly, sometimes difficult personalities, and these personal hangups can get in the way of effective pair programming. Author Oozie Ligus has logged over 700 hours of time pair programming and offers his advice on how to build an effective relationship.
Following "extreme programming" theory, a lot of software shops recommend pair programming as a good idea, but the literature is short on practicalities on how to make it work. Books like this offer a direct way forward to build software - and careers - through collaborative teamwork.
Given the informality of the cover, I didn't have high hopes for this book. The quality of the writing and the content, however, surprised me. He addresses best practices, worst practices, managing relationships, and personal growth. Though this book only covers 32 pages, the content clearly covers some depth of insight. For a short read, this book is well-worth the time for those interested in pair programming.
Found this book one morning before I was to give a workshop to our engineering team and I appreciated the guidelines / lessons learned compiled in this book. I’ll be sharing these with the team as we start embarking on our Pair Programming journey.