Keynote: Learning Is Teaching Is Sharing: Building a Great Software Development Team
summary
Company case studies show specifics: one firm sends 2000 engineers to two‑week C++ courses and later writes off a billion, while a fleet of 660 aircraft loses 219 aircraft before a culture of open near‑miss reporting halves accident rates. Concrete fixes recommended: use sanitizers, add small API wrappers, run rigorous code reviews as teaching moments, keep a bug‑sharing channel linking to cppreference/clang notes, require short regular practice sessions and pair reviews so knowledge transfer actually happens.
AI-written summary · about
chapters (10)
- 0:00Introduction and personal story
- 7:09Ericsson’s software failure in the 90s
- 15:22Swedish Air Force culture change
- 27:33API design and cognitive load
- 30:04Effective code reviews
- 36:40Communication in teams
- 43:08Continuous learning and training
- 48:35Toxic management and blame culture
- 53:04Building a culture of sharing
- 59:27Conclusion and reflections
related talks
01h 22mKeynote: Growing Better Programmers
43mKeynote: Coding Culture
28mLearning Out Loud: Cultivating a Culture of Learning on Engineering Teams
49mKeynote
52mKeynote: The Psychology of Code
48mWe're Good At Writing Software [Keynote]
32mOpening Keynote: The Good Bad Bug: Fail Your Way to Better Code
27m'The Art of Software Development'