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

Relying on tools

I don't trust tools. My friends and colleagues know that I'm often saying that Technology doesn't work. You might feel the same, or you might be more optimistic. For me, the more I have worked in software development, the more I don't trust tools, as I know they will fail at any moment. It's a given for me.

The only thing I have left, after passing through the usual states of frustration, acceptance, and resignation is to acknowledge that I need to have a second plan for any tool so that my work is not destroyed by the malfunction of the tool.

When talking about remote access, I tend to prefer a tool, but I always have another one as a backup. It has happened, on numerous occasions, that we started remote pairing on a tool and it stopped working in the middle of the session. Then, we agreed to immediately use the second backup tool. So, there you go. Here is the first suggestion I have for you:

Have a second backup remote access tool...