Pair Programming
A core practice in the Extreme Programming methodology, introduced by Kent Beck and others in the late 1990s. Two developers collaborate simultaneously on the same task: one acts as the driver writing code while the other navigates by reviewing and guiding. The practice is documented to significantly reduce defect rates.
Core Facts
Timeline (last 90 days)
Pair programming is a practice in Extreme Programming (XP): two developers share one machine and one keyboard, with one writing code (driver) and the other reviewing and thinking (navigator), switching roles periodically.
For teams that frequently do pair programming or code review, forking a session lets reviewers continue reasoning along the author's line of thought without having to interrupt the author.
Pair programming emphasizes real-time synchronization and low latency, while asynchronous takeover values branch traceability and audit logs more, and the two have different requirements for context consistency and permission control.
Pair programming is a software development practice in which the Driver writes code while the Navigator reviews it in real time and provides ideas, in order to improve code quality and knowledge sharing.
In traditional pair programming, two developers share a workstation—one writes code while the other reviews in real time—and practice has shown this reduces bugs and accelerates knowledge transfer.
Pair programming and code review are excellent scenarios for learning practical programming tips.
Traditional pair programming originated from the Extreme Programming (XP) methodology.
All Facts (8)
Pair Programming is one of the core practices in the Extreme Programming methodology proposed by Kent Beck in the late 1990s.
70%UnverifiedTraditional pair programming originated from the Extreme Programming (XP) methodology.
60%UnverifiedPair programming is a practice in Extreme Programming (XP): two developers share one machine and one keyboard, with one writing code (driver) and the other reviewing and thinking (navigator), switching roles periodically.
50%UnverifiedFor teams that frequently do pair programming or code review, forking a session lets reviewers continue reasoning along the author's line of thought without having to interrupt the author.
50%UnverifiedPair programming emphasizes real-time synchronization and low latency, while asynchronous takeover values branch traceability and audit logs more, and the two have different requirements for context consistency and permission control.
50%UnverifiedPair programming is a software development practice in which the Driver writes code while the Navigator reviews it in real time and provides ideas, in order to improve code quality and knowledge sharing.
50%UnverifiedIn traditional pair programming, two developers share a workstation—one writes code while the other reviews in real time—and practice has shown this reduces bugs and accelerates knowledge transfer.
50%UnverifiedPair programming and code review are excellent scenarios for learning practical programming tips.
50%