Egoless Engineering
summary
Argues that running teams at 100% utilization and hoarding responsibilities corrodes execution, using a 20‑person startup that added a useless Python middle layer and shipped nothing for two years and a 1,000‑person company that split managers into fracturing roles as evidence. Shows queuing blowups with Kingman's formula, describes a concrete fix where designers are given deploy keys and teams build monitoring, tests and deploy tooling which lets them ship again, and prescribes hack weeks and boot camps to expand cross‑team capability.
AI-written summary · about
chapters (15)
- 0:00Introduction and background
- 1:08Dividing responsibility problems
- 3:55Role subdivision gone wrong
- 6:21Creating new roles is a mistake
- 8:05Engineering throughput constraints
- 10:55Security team isolation issues
- 12:41Parochialism and ego in teams
- 13:22How functional teams succeed
- 16:31Empowering non-engineers
- 17:37Domain experts not owners
- 19:24Expanding psychological safety
- 21:11Cult leaders and humility
- 22:17Breaking cooperation deadlocks
- 23:18Leaders must value cooperation
- 24:22Misery as a bad proxy metric
related talks
45mEgo-less Programming: the Philosophy of Better Code
20mDoing Things the Hard Way
22mHow to be an inefficient developer?
01h 00mThe Empowered Software Engineer - unlocking engineering potential
43mBuild “boring” engineering orgs
39mImplementing Programmer Anarchy
58mReturn of the rockstars? Building great teams in challenging times
05mEngineering Without Dogma: When to Ignore the Best Practices