Pair programming is done through face-to-face environment. What if the pairs are separated in remote environments. Can it be done? or it will sink the productivity. This article will discuss how to make the pair programming, work well in remote environment. We have five tips that can be applied.
#1 Choosing the correct tools
Choose collaboration tools that support real-time code editing, screen sharing, and voice or video calls. Popular options include VS Code Live Share, JetBrains Code with Me, and collaborative IDE plugins. Make sure both participants install and test these tools before the session. My choice is
- Creating a group chat in MS Team for async communication
- Creating a Project Teams channel in MS Team for quick notes
- Choosing VS Code life share
#2 Communication Practices
Effective remote pairing hinges on open and continuous dialogue. Always verbalize your thought process as you type to keep both partners in sync
- Create schedule in your calendar
- Do daily stand up before pair programming
- Find a proper schedule for both parties
#3 Pairing Techniques
You need to calibrate your pair techniques based on situation
- Driver-Navigator: one person types (driver) while the other reviews each step and suggests improvements (navigator). Switch roles every 15–20 minutes to balance engagement and learning. this technique is recommended when you have tight deadline,
- Ping Pong: especially in test-driven workflows, alternate writing tests and implementing code. One writes a failing test, the other makes it pass, then swap roles. this is recommended to validate and refactor the coded
- Unstructured Pairing: once you’re comfortable with each other’s styles, allow fluid role changes as needed to maintain momentum. This is recommended when you need to calibrate with your pair
#4 Environment and Ergonomics
Agree on an IDE or editor configuration that both developers know. Avoid forcing a partner into an unfamiliar setup, as it doubles cognitive load and disrupts flow. For example,
- Use Development database in Azure so that you dont need to change configuration when switching the role
- Use similar codes convention to make familiar setups with pair
- Find good place to work together. Renting a private Co Workspace or cubicle is a good way to start
#5 Follow-up and Documentation
After each session, capture key decisions, open issues, and next steps in a shared document or pull request description. Commit with clear messages so that teammates can review the paired work efficiently.
- Creating a to do list for the next or current session
- documenting the knowledge in OneNote
- writing the finding in Azure Boards or Teams