Learning technical practices using mob programming
summary
Over six years of technical coaching uses mob programming as a deliberate learning tool: teams of about five or six sit around a screen with a projector and whiteboard, a desktop mob rotation app enforces role changes, and roles rotate roughly every 10–15 minutes. A strong-style pair programming rule keeps the navigator doing the thinking while the driver types. A 12-week apprenticeship batch teaches juniors TDD and refactoring; short-term delivery slows but trust, cross-team knowledge and long-term speed measurably improve.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 1:25About technical coaching
- 8:24Challenges with junior developers
- 10:54What is mob programming?
- 15:10Roles in mob programming
- 18:40Facilitator’s role and rules
- 22:12Why mob programming works
- 23:56Mob programming and team dynamics
- 29:42Q&A: Team speed concerns
- 31:14Q&A: Learning new languages
- 32:58Q&A: Strong style vs classic mob
- 34:02Q&A: Remote teams and mobbing
- 36:40Closing and book promotion
related talks
29mAccelerated learning with Mob Programming
12mTackling team dysfunctions with Mob programming -
31mMob Programming: Team-Building Included
46mMob Programming, the True Approach to Team Development
14mThe Tech Coach strikes back
26mMob Programming
01h 35mSoftware Teaming [Mob Programming] mini-workshop
01h 04mAdvanced Software Teaming