Picture a typical remote pairing attempt: two people join a video call, one shares the screen, the other turns off the camera "just for a moment". Two hours later, one has been typing nonstop while the other has quietly answered emails on the side. Both leave the call tired, and both conclude that pairing does not work remotely.
I see this pattern a lot, as a developer and as a team lead. In my experience, the problem is rarely the tool. It is the missing rhythm. I wrote a detailed guide on this, Remote pair programming: roles, timers and rotation, and this post sums up the ideas that matter most.
Pick a style on purpose
Pairing is not one technique. The style should match what you want to achieve:
- Driver and navigator is the all-rounder. One person handles the next concrete line, the other watches names, edge cases and the overall direction. You swap after a fixed time.
- Ping-pong suits test-driven work: one writes a failing test, the other makes it pass and writes the next one. Role switches happen naturally, and nobody can hide.
- Strong-style, based on Llewellyn Falco's rule that an idea has to travel through someone else's hands, is great for onboarding. The newcomer types, the experienced person explains. Treat it as a transition, not a permanent setup.
For decisions that affect everyone, ensemble (formerly mob) programming brings three or more people onto one piece of code. The Remote Mob Programming authors suggest rotating the typist roughly every ten minutes and consider three to four people the sweet spot. For routine work, it is usually too expensive.
Structure beats tooling
My advice for the first weeks: use whatever screen sharing or shared editor you already have. A new tool and a new way of working at the same time is too much. Turn cameras on, wear a decent headset and mute notifications.
What really makes the difference is a visible timer and planned breaks. Birgitta Böckeler and Nina Siessegger recommend Pomodoro blocks of about 25 minutes with short breaks, and see roughly six hours of pairing per day as the upper limit. If you work on separate machines, the open source tool mob takes care of Git handovers through a temporary WIP branch:
mob start 10 # start a session with a 10-minute timer
mob next # hand over the current state
mob done # squash everything back onto your branch
Bracket every session with five minutes at each end: agree on the goal, the starting roles and any constraints at the beginning, and do a tiny retrospective at the end.
Rotation and the human side
There are two kinds of rotation, and they work on different timescales. Roles inside a pair switch every few minutes. Who pairs with whom changes over days, ideally with a clear reason such as a finished topic or knowledge that so far sits in only one head. Changing pairs too often costs ramp-up time.
The most common pitfalls are not technical: a navigator who only watches, pairing as an all-day default, hierarchy that silently decides every question, and calendars full of meetings. As a team lead, I would not mandate pairing. Start it as a four-week experiment, protect calendar time, never use it as a control instrument, and join in yourself if you still write code.
I am convinced remote pairing is underrated for distributed teams, because it brings back the over-the-shoulder exchange that home office takes away. At the same time, I do not believe in pairing on everything. People differ, and a good team leaves room for both.
What the full article covers
- A closer look at all three pairing styles and when ensemble programming pays off
- A six-step setup for your first remote session, including tool options and the full
mobworkflow - Concrete starting values for rotating roles, typists and pairs
- Five common mistakes in detail and what team leads can do about them, plus a short FAQ
Read the complete guide: Remote pair programming: roles, timers and rotation
📖 This is the condensed version. The full article on sascha-ms.de goes deeper – with all code samples, diagrams and a short knowledge check.
👉 Next step: More for team leads: my cheat sheets put the essentials on one printable page.
📬 Stay updated: New articles on serverless, AI and leading tech teams via RSS, browser push or the weekly newsletter (in German).
Originally published on sascha-ms.de. More articles on serverless, AI in everyday development and leading tech teams: sascha-ms.de/en
Top comments (0)