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

How often do we need to pair?

This is a very common question that gets asked when using pair programming for the first time. The answer to this is very difficult since it depends heavily on the context of the organization, team, product, code, features, time available, and many other aspects. Let's answer some of the more common scenarios.

Should you pair for the whole day?

Especially at the beginning, pair programming can be extremely tiring. This is because we are doing activities that we aren't used to doing such as explaining every step, thinking about options, trying to explain alternative options, and more. Additionally, besides being tiring, pair programming is also very intensive. Due to these factors, I wouldn't recommend pairing for more than 1 or 2 hours per day, to begin with.

Once when you have paired for a while, and you have adjusted to how tiring it can be, you can pair for more than 1 or 2 hours per day. Maybe you can try pairing for half of...