9 min read • Guide 794 of 877
Pair Programming Organization
Pair programming produces better code and spreads knowledge. GitScrum helps teams coordinate pairing sessions and track collaborative work.
Pairing Benefits
Why Pair
PAIR PROGRAMMING BENEFITS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ CODE QUALITY: │
│ ───────────── │
│ • Two sets of eyes catch bugs earlier │
│ • Better design decisions │
│ • Built-in code review │
│ • Fewer defects reach production │
│ │
│ KNOWLEDGE SHARING: │
│ ────────────────── │
│ • Skills transfer between devs │
│ • No single points of failure │
│ • Faster onboarding │
│ • Team learns together │
│ │
│ FOCUS: │
│ ────── │
│ • Accountability keeps both on task │
│ • Less distraction (harder to check email) │
│ • Momentum through difficult problems │
│ │
│ TEAM: │
│ ───── │
│ • Builds relationships │
│ • Improves communication │
│ • Collective code ownership │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ WHEN TO PAIR: │
│ ────────────── │
│ ✅ Complex or unfamiliar code │
│ ✅ New team member onboarding │
│ ✅ High-risk changes │
│ ✅ Design decisions │
│ ✅ Debugging difficult issues │
│ ✅ Learning new technology │
│ │
│ WHEN NOT TO: │
│ ───────────── │
│ ❌ Simple, routine tasks │
│ ❌ When both are exhausted │
│ ❌ Individual research/reading │
│ ❌ Administrative tasks │
└─────────────────────────────────────────────────────────────┘
Pairing Structure
Driver-Navigator Model
DRIVER-NAVIGATOR ROLES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ┌───────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ DRIVER NAVIGATOR │ │
│ │ ────── ───────── │ │
│ │ │ │
│ │ ⌨️ Has keyboard 👀 Watches screen │ │
│ │ 📝 Types code 🗺️ Thinks ahead │ │
│ │ 🔧 Implements 💡 Suggests direction │ │
│ │ 🎯 Focuses on now 🔭 Sees big picture │ │
│ │ │ │
│ │ "I'm typing the "We should probably │ │
│ │ function now" think about error │ │
│ │ handling here" │ │
│ │ │ │
│ └───────────────────────────────────────────────────────┘ │
│ │
│ SWITCHING: │
│ ────────── │
│ • Every 15-30 minutes │
│ • At natural breakpoints │
│ • When navigator has idea to implement │
│ • When driver gets stuck │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ TIPS: │
│ │
│ FOR DRIVER: │
│ • Think out loud │
│ • Ask "What do you think?" │
│ • Don't just type silently │
│ • Accept suggestions gracefully │
│ │
│ FOR NAVIGATOR: │
│ • Stay engaged (don't check phone) │
│ • Give space to think │
│ • Suggest, don't dictate │
│ • Watch for bigger issues │
└─────────────────────────────────────────────────────────────┘
Session Planning
PAIRING SESSION STRUCTURE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ BEFORE SESSION: │
│ ─────────────── │
│ │
│ SCHEDULE: │
│ • Book 2-4 hour blocks │
│ • Don't schedule back-to-back sessions │
│ • Morning often better (fresher minds) │
│ │
│ PREPARE: │
│ • Clear goal for session │
│ • Relevant context shared │
│ • Environment set up │
│ • No other meetings during │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ SESSION PLAN: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ PAIR-SESSION: Auth Refactoring ││
│ │ ││
│ │ PARTICIPANTS: @alex (driver first) + @jordan ││
│ │ DURATION: 3 hours ││
│ │ TASK: STORY-789 - Refactor auth module ││
│ │ ││
│ │ GOAL: ││
│ │ Refactor authentication to support SSO ││
│ │ while maintaining current login flow ││
│ │ ││
│ │ CONTEXT NEEDED: ││
│ │ • Current auth flow diagram ││
│ │ • SSO provider documentation ││
│ │ • Test accounts ││
│ │ ││
│ │ STRUCTURE: ││
│ │ 0:00 - Review current code together ││
│ │ 0:30 - Design new approach ││
│ │ 1:00 - Implement (switch every 25 min) ││
│ │ 2:30 - Write tests ││
│ │ 3:00 - Wrap up, document decisions ││
│ │ ││
│ │ BREAKS: 5-10 min every hour ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ DURING SESSION: │
│ ─────────────── │
│ • Set timer for role switches │
│ • Take breaks (pomodoro works well) │
│ • Stay on task │
│ • Communicate constantly │
│ │
│ AFTER SESSION: │
│ ────────────── │
│ • Update task status │
│ • Note what was completed │
│ • Document any decisions │
│ • Quick retro: "What worked? What didn't?" │
└─────────────────────────────────────────────────────────────┘
Remote Pairing
Tools and Setup
REMOTE PAIRING SETUP:
┌─────────────────────────────────────────────────────────────┐
│ │
│ TOOLS: │
│ ────── │
│ │
│ SCREEN SHARING: │
│ • VS Code Live Share (best for code) │
│ • Tuple (purpose-built for pairing) │
│ • Zoom/Meet (screen sharing) │
│ │
│ COMMUNICATION: │
│ • Video ON (see reactions, stay engaged) │
│ • Good microphone │
│ • Headphones (avoid echo) │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ VS CODE LIVE SHARE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ BOTH CAN: ││
│ │ • Edit code simultaneously ││
│ │ • Navigate independently ││
│ │ • Run terminal commands ││
│ │ • Debug together ││
│ │ ││
│ │ FEATURES: ││
│ │ • Follow mode (see what partner sees) ││
│ │ • Shared terminals ││
│ │ • Shared localhost ││
│ │ • Works cross-platform ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ REMOTE PAIRING TIPS: │
│ ───────────────────── │
│ ✅ Video on (engagement, non-verbal cues) │
│ ✅ Verbalize more (can't see body language) │
│ ✅ Share screen with low latency │
│ ✅ Take more breaks (screen fatigue) │
│ ✅ Use follow mode intentionally │
│ ❌ Don't let one person take over │
│ ❌ Avoid multitasking on other screen │
└─────────────────────────────────────────────────────────────┘
Pairing Patterns
Different Approaches
PAIRING STYLES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ EXPERT-NOVICE: │
│ ────────────── │
│ Purpose: Learning, onboarding │
│ │
│ • Novice drives, expert navigates │
│ • Expert guides but doesn't take over │
│ • Novice asks questions freely │
│ • Switch when novice comfortable │
│ │
│ CAUTION: Expert should not just dictate │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ PEER PAIRING: │
│ ───────────── │
│ Purpose: Collaboration, shared ownership │
│ │
│ • Equal skill levels │
│ • Regular role switching │
│ • Discuss approaches together │
│ • Both contribute ideas │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ PING-PONG (with TDD): │
│ ───────────────────── │
│ Purpose: Test-driven development │
│ │
│ 1. Person A writes failing test │
│ 2. Person B writes code to pass │
│ 3. Person B writes next failing test │
│ 4. Person A writes code to pass │
│ 5. Repeat... │
│ │
│ Good for: Focused TDD, keeping tests first │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ MOBBING: │
│ ──────── │
│ Purpose: Whole team on complex problem │
│ │
│ • 3+ people, one driver │
│ • Rotate driver frequently (5-10 min) │
│ • Everyone contributes as navigator │
│ • Good for design decisions, complex bugs │
│ │
│ CAUTION: Expensive - use for high-value problems │
└─────────────────────────────────────────────────────────────┘
Common Challenges
Pairing Problems
PAIRING CHALLENGES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ "ONE PERSON DOMINATES": │
│ ──────────────────────── │
│ Problem: Driver never switches, navigator passive │
│ Fix: Strict timer for switching │
│ Fix: Navigator should drive more │
│ Fix: Use ping-pong style │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ "EXHAUSTING AFTER FEW HOURS": │
│ ────────────────────────────── │
│ Problem: Pairing is intense │
│ Fix: Take regular breaks (pomodoro) │
│ Fix: Don't pair all day │
│ Fix: Mix pairing with solo work │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ "WE DISAGREE ON APPROACH": │
│ ────────────────────────── │
│ Problem: Conflict about how to solve │
│ Fix: Discuss before coding │
│ Fix: Try both approaches briefly │
│ Fix: Get third opinion │
│ Fix: Default to simpler solution │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ "SKILL GAP TOO LARGE": │
│ ─────────────────────── │
│ Problem: Expert frustrated, novice lost │
│ Fix: Expert explains more │
│ Fix: Novice drives │
│ Fix: Pair on appropriate complexity │
│ Fix: Pre-session context sharing │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ "FEELS SLOWER": │
│ ─────────────── │
│ Problem: Manager thinks pairing wastes time │
│ Reality: Often faster overall │
│ - Fewer bugs to fix later │
│ - Less rework │
│ - Built-in code review │
│ - Knowledge doesn't get stuck │
│ │
│ Measure: Time to done (including bugs), not just coding │
└─────────────────────────────────────────────────────────────┘