In praise of “normal engineers”
summary
Argues that excellence comes from systems not unicorn hires and claims a huge competitive advantage from designing for normal engineers who can ship, observe, and iterate daily. Recommends precise hires for the business, shrinking the write→live loop, owning deploys and rollbacks, investing in observability and developer platform tooling, and composing multi‑level teams rather than hunting the top 10%/0.1%. Gives concrete levers and cultural practices to make ordinary engineers productive.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 1:05Why I wrote about normal engineers
- 2:54Flaws in the 10x engineer myth
- 6:04Teamwork beats individual brilliance
- 8:50Normal engineers can do great work
- 13:32Problem with hiring top talent
- 14:37What does normal mean
- 17:26Fundamental attribution error in tech
- 18:49Alignment matters more than speed
- 20:37Hiring for strengths not lack of weaknesses
- 21:40Precision in excellence
- 23:25Systems for normal engineers
- 24:52Sociotechnical systems principles
- 27:18Inclusive culture and diversity
- 28:45Balanced teams over hierarchies
- 29:47Excellence without compromising standards
- 30:53Investing in people and learning
related talks
23mGad Salner- How to scale a unicorn-building engineering team (and stay sane)
06mRemoving engineering friction: Creating an evolutionary culture
51mDon’t Feed the Pigeons Some Principles from Real World Internal Developer Platform
58mReturn of the rockstars? Building great teams in challenging times
31mThe Effective Developer - Work Smarter, Not Harder
47mBuilding software products distilled: customer value, engineering and delivery
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
15mOptimizing the engineering value stream