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

Learning to use source control

Let's look at some guidelines on how to use source control in a (remote) pair programming context. Some people might even enforce these guidelines and call them rules, making them part of the coding guidelines of the team. The most important thing is that the team understands why it's important to respect these guidelines.

Source control tools

Like any programmer, I have some favorite tools. Yours may be different, and that is fine. I want to explain why I use a distributed source control, and why I would never go back to centralized source control.

When I started programming, we were using these tools such as CVS, SVN, and Source Safe to manage code contributions. There were many teams who didn't have any source control, and I always found that scary. From the start, using Source Safe didn't feel safe at all. It would lose files and references, and it was never a reliable tool. CVS was complicated to use; you needed a lot...