Mob Mentality Collaborative Coding and Problem Solving
summary
Claim: sitting a whole team at one screen raises code quality, learning speed, and morale while shrinking feedback loops. Practice details: one screen, one keyboard driver/navigator, a facilitator, and rotate every four minutes with frequent commits and tests so mistakes surface immediately. Techniques used: consume-first coding, “intent / location / keystrokes” calls, TDD and refactoring katas. Evidence: a 20‑minute kata gives more learning than a day; a 3‑day Vue.js mob brings novices to real proficiency; typical session is three hours with a 30‑minute retro.
AI-written summary · about
chapters (6)
- 0:00Introduction to mob programming
- 3:53Why mob programming works
- 14:55How mob programming is structured
- 28:01First mob programming session tips
- 38:03Rules for effective mobbing
- 46:37Closing and retrospectives
related talks
01h 04mAdvanced Software Teaming
01h 00mMob Programming, A Whole Team Approach
01h 35mSoftware Teaming [Mob Programming] mini-workshop
29mAccelerated learning with Mob Programming
37mLearning technical practices using mob programming
41mTurn Up the Good
50mMob Programming, A Whole Team Approach
26mMob Programming