A software development technique where two
programmers work together at one workstation One will
act as the driver and the other as the navigator, but
these roles will switch frequently.
DRIVER
- Owns the keyboard/mouse
- Asks clarifying questions
- Focuses on task at hand
NAVIGATOR
- Explains the “what” and “why” of the code
- Focuses on the bigger picture
- Ongoing code review
BOTH ROLES
- Both programmers must be actively enagaged - you
should be paying enough attention that the roles could
be swapped at any time
- Pairing should result in some mental fatigue due to
how much you haveto focus - this is why pairing can
often lead to faster results
BENEFITS
- Improves quality
- Takes less timeSolidify and deepen understanding
ofmaterial
- Shore up weaknesses
- Constant engagement
PARTNER COMPATIBILITY
Pairing works best when partners are of a similar
skill level, but no two people will have identical skill
sets.
TIPS
- Be sure to talk - “programming out loud”
- Be actively engaged
- Rotate roles frequently; start at 20 minutes, but
feel free to adjust
- No keyboard hogging
- Be patientBe prepared - lesson material and
hygiene!
- Do not be intimidatedDo not suffer in silence