Solutional
Pair programming is an agile software development practice in which two developers work on the same task together. They may share one workstation or use separate keyboards, mice, and monitors connected to the same computer. Our office setup uses one computer, two keyboards, two mice, and two mirrored displays.
How Pair Programming Works
Q: What do the two developers do?
A: One developer acts as the driver and writes the code. The other acts as the observer and reviews the work as it happens. The pair discusses design choices, catches mistakes early, and switches roles regularly.
Q: How does the observer help the driver?
A: The observer lets the driver focus on implementation while keeping an eye on the wider problem. They can suggest alternatives, notice potential bugs, and ask questions before a weak decision becomes embedded in the code. Pair programming is a practical example of the idea that two heads are often better than one.
Q: Would two developers be more productive on separate tasks?
A: Sometimes, but not always. Pair programming increases focus, shortens feedback loops, and reduces time spent working through difficult problems alone. Breaks still matter, but the pair usually takes them together and returns to the task with shared context.
Benefits and Drawbacks of Pair Programming
Results vary by team, project, and personality, but our experience has highlighted the following points.
Benefits:
- Shared ownership of the codebase
- Better focus on the task
- Fewer defects and earlier feedback
- Faster onboarding for new developers
- Stronger communication within the team
- Continuous knowledge sharing
- Quick design discussions that improve production code
- Less time spent solving difficult problems alone
A few minutes of focused discussion can prevent hours of trial and error.
Drawbacks:
- Pair programming does not suit everyone
- It fails when one developer is not actively involved
- It requires both people to listen, explain their reasoning, and work as a team
- It can be inefficient for small, routine, or easily divided tasks
Does Pair Programming Cost Twice as Much?
Not necessarily. The answer depends on the size and complexity of the project. For a small, straightforward task, pairing may add little value. For a long-running or technically demanding project, better design decisions, fewer bugs, shared knowledge, and faster onboarding can reduce total cost over time.
Pair programming is a broad topic, and no single approach works for every team. For further reading, see this collection of scientific research on pair programming.
