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 line and thinks ahead (the "navigator").

Why it exists

• Bugs and design issues caught during writing, rather than in a separate later review, are typically cheaper to fix
• Working alone means only one perspective catches mistakes and considers alternative approaches in the moment

How to apply it

• Switch driver/navigator roles regularly so both people stay actively engaged rather than one just watching
• Use it selectively for complex or high-risk work, rather than assuming it should replace all solo development time

FAQ

Does pair programming slow teams down?

It uses two people's time for one task in the moment, but proponents argue this is often offset by fewer bugs, less rework, and knowledge spreading faster across the team.