Pair Programming as a Mechanism for Growth
summary
Claim: pair programming accelerates developer growth through concrete practices not platitudes — seniors reorganize knowledge by explaining, juniors learn far faster via apprenticeship, and teams catch bugs and design issues together. Specifics include 20–25% of time pair programming at a company with an Ember front end and Rails backend, using psychological safety and the rule to wait ten seconds before correcting typos. Anecdotes show a rubber‑duck dialogue that fixes a deployment bug and uncovers another.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:07What is pair programming?
- 2:36Why talk about pair programming?
- 4:22How can it help you grow?
- 6:00Why should you listen to me?
- 7:35'Member being a beginner?
- 9:15Drop expectations of what your partner "should" know
- 10:35Establish Psychological Safety
- 11:45Don't be dismissive of your partner's ideas
- 14:03Start with an approach discussion
- 14:36Guide your pair through solving the problem for themselves
- 16:17Explain things more better
- 18:03Let the junior dev drive
- 20:07Have the right mindset Part 1
- 20:48Have the right mindset Part 2
- 22:09You can contribute more than you may think
- 24:50Don't be afraid to say you don't understand
- 25:39Ask Better Questions
related talks
23mWarm-Up Talk: Perceptions of Pair Programming
43mPair Programming Pragmatically
41mPair Programming
32mMaximizing the Fun Pair Programming Benefits
28mProblem Solving Through Pair Programming
44mWhat We Learned in 8829 Hours of Pair Programming
32mHow to work as a team, sleepy to strong pair programming
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming