What Is Pair Programming?

Pair programming is a practice where two developers work together at one workstation — one actively writing code (the "driver") while the other reviews each...

Published October 8, 2026

Pair programming is two developers working together at one workstation: one writes code (the driver) while the other reviews and thinks ahead (the navigator). It improves quality and spreads knowledge.

The concept

Roles swap often. The navigator catches mistakes early and considers design while the driver focuses on syntax.

It works well for tricky problems, onboarding and spreading knowledge, and less well for trivial tasks.

Two roles

swapDrivertypesNavigatorreviews, plans
Swap roles every 15–30 minutes.

Practical examples

Ping-pong with TDD

A writes a failing test → B makes it pass → B writes the next failing test → A makes it pass

Remote pairing

Screen share + VS Code Live Share, voice call open

Session rhythm

25 min pair · 5 min break · swap roles

Common mistakes

  • One person dominating the keyboard.
  • Pairing all day, every day.
  • Skipping breaks.

Key takeaways

  • Driver + navigator, swap often.
  • Great for hard problems and onboarding.
  • Use selectively.

FAQ

Is it slower?

Output per hour may drop, but defects and rework usually fall.

What is mob programming?

The whole team works on one task at one computer.

More General articles