Build “boring” engineering orgs
summary
Argues that companies gain a competitive edge by making ordinary engineers productive through concrete changes: keep a short deploy interval (avoid six‑month lag), give every engineer the ability to deploy‑own‑code and use feature flags, invest in observability and fast CI so traces show where time goes, set internal SLOs for test/deploy latency, staff a platform team to make doing the right thing easy, hire for communication and diversity, and compose mixed‑level teams so normal engineers consistently ship and the org “mints” world‑class engineers.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:0210x engineers to normal engineers
- 6:58Teams own software
- 16:08Building 10x teams
- 19:21Short deploy intervals
- 21:26Observability and tooling
- 23:11Internal tools and productivity
- 23:53Learning and inclusive culture
- 26:26Diverse skill teams
- 31:03Excellence is learnable
- 36:00Conclusion and hiring
- 39:11Q&A
related talks
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
47m‘Engineering' for Software - How to Amplify Creativity
06mRemoving engineering friction: Creating an evolutionary culture
48mHow to Build and Maintain Engineering Teams Focused on Product through Culture and Values
28mBuilding happier engineering teams
42mBuilding a Strong Engineering Culture – Stacy Devino
22mA Plea for Boring Tech
52mSecrets of a Strong Engineering Culture