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

Improving source control usage

There is more to source control than using good commits or having ensemble commits. Bad usage of source control is amplified when pairing remotely, thus it's even more important to respect some best practices.

Here is a list of the best practices I use for source control, which may already be familiar to you, in the form of a checklist:

  • Use source control in any situation, no matter how small the project is.
  • Add all resources to the source control (code, libraries, scripts, configuration, and so on).
  • Check that your source control repository is functional before starting the project.
  • Review the changeset before committing/pushing.
  • Make sure newly added libraries are in the changeset as well.
  • Only commit files that have meaningful changes (not non-behavioral changes such as spacing, alignment, styling, and so on).
  • Use clear—ideally standardized—commit messages (start from the Linux kernel conventions...