In 30 seconds
- Driver writes code; navigator reviews and guides.
- Swap roles often.
- Fewer defects and faster knowledge sharing.
Roles
- Driver: types and focuses on the immediate code
- Navigator: reviews each line and thinks about direction
A core Extreme Programming practice.
Pairing styles
| Style | How |
|---|---|
| Driver-navigator | Classic split, swap every so often |
| Ping-pong | One writes a failing test, the other makes it pass |
| Strong-style | Ideas must go through the other person's hands |
Benefits and costs
Pairs typically produce fewer defects, spread knowledge and onboard people faster. It can be tiring, so take breaks and don't pair on everything. Pairing replaces much of the need for separate code reviews.
Myth vs reality
Myth · Pairing halves output.
Reality · Fewer defects and less rework often make up for it.
Myth · Pairs should be senior with junior.
Reality · Every combination has value.
Myth · Pairing must be all day.
Reality · A few focused hours a day is common.
The AI angle
AI assistants can act as a pairing partner for routine work, but they don't share knowledge across the team or own the result. Keep human pairing for design and risky changes.
FAQ
How often should we switch pairs?
Many teams rotate daily or every few days.
Does remote pairing work?
Yes, with screen sharing and good audio.
What if pairs disagree?
Try both ideas quickly, or ask a third person.