Expertise vs Experts
summary
Claims that knowledge must live in artifacts not heads and reports a practice that converts experts into expertise providers: 100 people across 25 projects run for four years with no meetings, no Slack, only GitHub tickets, and emphasize readable code and examples. Cites 35% annual job turnover and builds an AI project-management chatbot that pulls repo configs, runs Docker builds and deploys. Compensation ties to delivered results—pay for results—so knowledge is pushed into scripts, tests and docs rather than retained.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:17The Trends
- 8:13The Problem
- 12:13The Solution
- 16:37Don't learn how it works, make sure it doesn't need to be learned
- 22:10Good programmers know how to explain, the best ones know how to write.
- 24:25Knowledge Accumulating Experts
- 25:01The best engineers are the easiest to replace.
related talks
46mKeynote: Costs of the Cult of Expertise
49mExtreme Professionalism - Software Craftsmanship.
32mCode First, Ask Questions Later
28mHow To Not Be An Expert
38m"My Experience With Experience"
20mSeeing the Invisible: Discovering Operations Expertise
45mThe DevOps Revolution: We Haven't Always Known Everything
24mWhen expertise becomes our achilles heel