Book Image

Practical Remote Pair Programming

By : Adrian Bolboacă
Book Image

Practical Remote Pair Programming

By: Adrian Bolboacă

Overview of this book

Remote pair programming takes pair programming practices to the next level by allowing you and your team members to work effectively in distributed teams. This helps ensure that you continuously improve code quality, share equal ownership of the code, facilitate knowledge sharing, and reduce bugs in your code. If you want to adopt remote pair programming within your development team, this book is for you. Practical Remote Pair Programming takes you through various techniques and best practices for working with the wide variety of tools available for remote pair programming. You'll understand the significance of pair programming and how it can help improve communication within your team. As you advance, you’ll get to grips with different remote pair programming strategies and find out how to choose the most suitable style for your team and organization. The book will take you through the process of setting up video and audio tools, screen sharing tools, and the integrated development environment (IDE) for your remote pair programming setup. You'll also be able to enhance your remote pair programming experience with source control and remote access tools. By the end of this book, you'll have the confidence to drive the change of embracing remote pair programming in your organization and guide your peers to improve productivity while working remotely.
Table of Contents (14 chapters)
1
Section 1: Introduction to Pair Programming
5
Section 2: Remote Pair Programming
9
Section 3: Tools to Enhance Remote Pair Programming

Situations when pair programming is difficult

Pair programming is not just cookies, candies, and sweets all the time. It can also become a bitter experience in some situations. We shouldn't force anyone to use pair programming, as it's not for everybody. It's a good practice, a good tool, but as with anything, there are exceptions. Let's see some typical situations where pair programming is difficult to use, or where it shouldn't be used at all.

Working alone

There are people who like working alone and who are efficient in doing so. For them, collaboration is difficult, and going to meetings seems like a waste of time. For these people, pair programming is really difficult, and we need to check if it is a good idea to bring them onto the pair programming bandwagon.

It might be debatable if such a programmer has a place in the team. Regular team players might think that such a person should be fired because they don't play by the team rules. On...