---
id:"kb-2026-00238"
title:"Pair Programming"
schema_type:"TechArticle"
category:"computer-science"
language:"en"
confidence:"high"
last_verified:"2026-05-22"
generation_method: "human_only"
ai_models:["claude-opus"]
derived_from_human_seed:true


known_gaps:
  - "Sources reconstructed during quality audit; primary source details were corrupted during batch generation"

completeness: 0.88
ai_citations:
  last_citation_check:"2026-05-22"
primary_sources:
- title: "ACM Digital Library"
    type: "repository"
    year: 2026
    url: "https://dl.acm.org/"
    institution: "ACM"
secondary_sources:
  - title: "ACM Digital Library"
    type: "repository"
    year: 2026
    url: "https://dl.acm.org/"
    institution: "ACM"
---

## TL;DR

Pair programming (part of XP, Kent Beck) is two developers working at one computer: Driver (writes code) + Navigator (reviews each line, thinks strategically). Roles switch frequently. Studies show 15% more effort but 15% fewer defects — net quality improvement. Extremely effective for complex problems and knowledge transfer.

## Core Explanation

Styles: Driver-Navigator (one codes, one reviews), Ping-Pong (TDD: one writes test, other makes it pass), Strong-Style (novice drives, expert navigates — for knowledge transfer). Benefits: continuous code review, knowledge sharing, better design (two minds), reduced distractions. Not effective for: simple/mechanical tasks, when developers can't get along.

## Further Reading

- [Extreme Programming Explained (2nd Ed, Kent Beck)](undefined)