Burn Rubber Does Not Mean Warp Speed
summary
Argues rapid developer training (24 hours to six months) produces bad assumptions and weak outcomes, contrasts with historical apprenticeships measured in years, and recommends concrete fixes: structure a two-year apprenticeship with a possible three-year contract, require mentor training, rotate apprentices as internal journeymen, and track progress with a measured backlog and retrospectives plus holistic metrics (team fit, communication, business value) instead of only lines of code or velocity.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:13apprenticeships.
- 5:44on your mark
- 9:20journeyman
- 10:03master.
- 12:39what's so scary?
- 15:32employers.
- 16:29pit of despair
- 20:19what's missing?
- 20:55growing up fast.
- 21:57teacher training.
- 22:51what's important?
- 24:43two way street.
- 26:41time
related talks
30mBurn Rubber Does Not Mean Warp Speed
49mApprenticeship programs
52mGreat Expectations: Power-Charging Apprenticeship Programs
32mThe Practical Guide to Building an Apprenticeship
27mDeveloping Developers
25mSoftware Craftsmanship's Missing Link: Apprenticeship
48mBe ‘Mr Miyagi’ or find one!
38mHow a Culture of Mentorship and Collaboration Makes You Grow 10x Faster