Learning through Osmosis
summary
Teams work on one task at one keyboard so everyone learns by watching and doing, using one computer with a rotating driver who follows commands and a designated navigator who gives high‑level intent; rotate about every four minutes, groups of 6–10 scale down or split. Mobs run weekly or full days (Hunter runs them 8h/day), and are used for feature work, TDD, security and performance scripts; surprising result: non‑programmers and even a nine‑year‑old ship working code and novices become contributors, improving communication and delivery.
AI-written summary · about
chapters (36)
- 0:00Intro
- 1:29I identify well
- 2:30Learning through osmosis
- 3:48Childhood
- 5:29Change in mindset
- 5:45My story
- 7:53Testing
- 10:58Programming for kids
- 12:12Teaching kids programming
- 13:22Woodys whale
- 17:58Feeling Safe
- 19:16Correcting Mistakes
- 20:11Relevance
- 20:40Communication
- 21:49All Female Hackathon
- 24:46Programmer
- 26:18Mechanics
- 26:33Testers
- 27:43Driver
- 28:48Navigator
- 30:53Roll Chair
- 31:56Retrospective
- 32:22Group size
- 33:05Two ideas
- 34:17Best ideas win
- 34:52Level level ideas
- 35:20Osmosis
- 37:20Mobile testing
- 38:01Cognitive dissonance
- 39:13Accidental learning
- 40:09Continuous learning
- 40:56Learning cumulates
- 41:23Learning is multidimensional
- 41:53Experts no longer know the most
- 43:42Testing is fun
- 45:08Through experience
related talks
50mMob Programming, A Whole Team Approach
26mMob Programming
37mLearning technical practices using mob programming
29mAccelerated learning with Mob Programming
46mMob Programming: A Whole Team Approach
01h 00mMob Programming, A Whole Team Approach
01h 35mSoftware Teaming [Mob Programming] mini-workshop
54mMob Mentality Collaborative Coding and Problem Solving