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

Using the commit types

The commit types were part of the previous checklist for best source control practices. We need to elaborate on these commit types as follows, and see how they can help you with each of the preceding scenarios:

  • New feature: I found it useful to have a focus factor, and since I am always using a clear list of prioritized features that remain important for the next few days, it was evident that changesets need to relate to that feature. That's why whatever change I do (config file, database, adding a library, changing an application programming interface (API), adding a code file, changing existing code, and so on) needs to be related to the feature I am working on. It's easy for me and my team to grasp changes when it's clear that a commit matches a particular feature as shown here:
    commit d6a3b90e95b5e4f356c4236b55707a21465ca67z
    Author: Adrian Bolboacă <[email protected]> 
    Date:   Thu May 28 09:05:15 2020 +0200 
     
        New feature...