references/knowledge/pair-programming.md

<!-- Generated from skills/pair-programming/SKILL.md; edit the canonical source. -->

# Pair Programming for Learning

**Evidence tier: moderate.** Williams & Kessler's studies show learning and quality gains with modest effect sizes; strong-style pairing is practitioner-derived.

## Strong-Style Pairing (Falco, 2014)

"For an idea to go from your head into the computer, it must go through someone else's hands."
- The person with the idea navigates (describes intent)
- The other person drives (types code)
- Forces explicit communication of thinking
- Designed specifically for coaching junior developers

## Driver/Navigator Model (Freudenberg)

- **Driver**: Tactical — writes code, manages files
- **Navigator**: Strategic — reviews, thinks ahead, maintains mental model
- They form a "cognitive tag team" that reduces overload

## Ping-Pong Pairing with TDD

1. Person A writes a failing test
2. Person B makes it pass
3. Person B writes the next failing test
4. Repeat

Ensures both participants engage with specification, implementation, and refactoring.

## Williams & Kessler Research (2000, 2002)

- 90% of participants preferred pairing over solo work
- Pairing increased software quality and decreased development time
- Students showed higher retention and reduced course drop-outs
- Collaborative nature facilitated knowledge transfer and deeper understanding