Pair Programming: Poop & Pee adventures
summary
Examines practical problems and social dynamics of pair programming, naming issues like power imbalances, different mental processes, driver/navigator style clashes, and onboarding when partners have unequal product knowledge. Covers the need to adjust tempo, maintain patience and not make a pair feel bad for lagging, argues that pairing can eliminate the need for merge/pull requests, and even addresses the mundane awkwardness of using the restroom while paired.
AI-written summary · about
chapters (18)
- 0:00Pair programming intro
- 3:14Pair benefits and challenges
- 7:06Pair limitations and costs
- 9:12Pair roles types
- 10:38Pair programming techniques
- 13:27Role combinations and dynamics
- 16:36Power dynamics in pair
- 20:30Overcoming power dynamics
- 23:00Diversity and team success
- 27:08Work environment and tools
- 28:54Puppy effect
- 29:56Safe environment for pair
- 31:00Personal pair experiences
- 33:27Who can pair program
- 36:34Trust in pair programming
- 41:19Pair in multidisciplinary teams
- 45:55Respecting pair preferences
- 47:41Camera importance in remote pair
related talks
43mPair Programming Pragmatically
23mWarm-Up Talk: Perceptions of Pair Programming
28mPair Programming as a Mechanism for Growth
41mPair Programming
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
53mFour Cases of Pair Programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
32mMaximizing the Fun Pair Programming Benefits