Un-becoming the bottleneck
summary
Claims a concrete win: a bespoke data engineering diagnostic tool gets built and deployed to let team members diagnose ad-delivery problems themselves, and it works — incidents get resolved without intervention. Growth happens by carving time to mentor three strong engineers weekly, pushing them into unfamiliar parts of the system, and letting them bang their heads before answering. The result: critical migrations and production issues proceed with redundancy, proving investing in 2–3 people outperforms broadcasting org-wide advice.
AI-written summary · about
chapters (6)
- 0:00Hero complex costs
- 1:33Growth bottleneck
- 2:17First parental leave
- 4:27Second parental leave
- 5:51Empowering tools
- 8:58Scaling by growing others
related talks
06mRemoving engineering friction: Creating an evolutionary culture
26mMore Culture, More Engineering, Less Duct Tape v3.0
02h 31mDeveloper Productivity Engineering - Extended Session
34mBecoming a team, one pixel at a time
44mEnhancing the Performance of Engineering Teams
27mLessons from a Year with Backstage: What Worked, What Didn’t...
31mIntegrating an expert solo developer into a development team
20mBuilding High-Productivity Teams Focused on Outcomes: Team Design and Collaboration Case Studies