Fostering a learning culture in coding teams
summary
Interviews with 25 developers and 30+ hours of think‑aloud coding sessions produce a concrete claim: teams create learning debt when onboarding and review practices punish exploration. Findings include concrete measures — developers report less than 10 percent of code is well commented — and a mechanism: an emergent performance culture that silences learning and propagates secrecy. Recommendation is specific: measure, recognize, and reward learning behaviors so exploration and mistakes are preserved as engineering assets.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:28Story
- 3:21Learning debt
- 3:59The study
- 5:48Real voices
- 6:50Performance culture
- 7:41Conclusion
related talks
45mMaking Learning Conscious — How and why to build a learning culture
01h 02mAround Learning
05mCultivating a Learning Culture: Unlocking the Power of Continuous Development
01h 02mWhen will you learn? A Teacher’s Guide to Developer Learning
18mBuilding a Culture of Code Quality
29mActive Learner - How developers keep learning
30mLessons Learned: A Developer's Perspective on Teaching & Learning
34mBuilding a Culture For Developer Productivity