Learning Out Loud: Cultivating a Culture of Learning on Engineering Teams
summary
Three concrete practices: default to not knowing by asking clarifying questions and read docs together instead of sending links; champion public problem solving by creating a “no stupid questions” Slack channel, linking threads into JIRA and documenting decision rationales; and formalize spontaneous learning with study sessions, designated office hours (for example C++ office hours), and paid mentoring time. These steps produce more written documentation, wider redundancy, earlier incident detection (a “blameless premortem”), and measurable gains in retention and job satisfaction.
AI-written summary · about
chapters (7)
- 0:00Introduction and exercise
- 1:26I don’t know is a superpower
- 3:10Defaulting to not knowing
- 7:04Championing public problem solving
- 14:27Formalizing spontaneous learning
- 21:33Benefits of learning culture
- 27:49Q&A and closing
related talks
14mIt's Like Coding in the Dark: the Need for Learning Culture in Engineering Teams
05mCultivating a Learning Culture: Unlocking the Power of Continuous Development
52mThe Path to Knowledge — How to Build a Continuous Learning Culture
38mBuilding a Strong Engineering Culture – Chuck Greb
28mCultivating a culture of Psychological Safety in Engineering
19mTeam Culture: How the little things enable great outcomes
01h 00mKeynote: Learning Is Teaching Is Sharing: Building a Great Software Development Team
27mCultivating ownership at any engineering level