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

Recap of main concepts of pair programming

When we're learning about something, we say that repetition is the mother of learning. So, let's repeat, in short, the main concepts of pair programming techniques and styles:

  • The driver is the one writing the code and focuses on small details. Usually, the driver is in charge and makes all the decisions.
  • The navigator observes the driver writing the code and focuses on long-term decisions. Also, the navigator suggests ideas, comes up with options, and shows the potential risks, dangers, or drawbacks of the current code.
  • Rotation is the moment when the driver and the navigator change roles: the driver becomes the navigator and vice versa. Depending on the technique and style, it can happen more or less often, or it can even not happen at all.
  • Setup refers to what you need to start your pair programming session: computer(s), an extra keyboard, a mouse, source control access, video, audio, screen sharing, an IDE...