How to become obsolete
summary
Shows how a lead intentionally makes themself replaceable by teaching pair programming and the Socratic method, running weekly one‑on‑ones, and sharing ownership so two co‑tech leads can swap duties. Describes building the Glass UI library, rolling out clang sanitizers, and catching a CI‑detected Neoverb performance regression that delays a release — concrete failures and fixes, public Q&A from Slack, pairing for debugger watchpoints, and a forum that assigns volunteers to own cross‑company initiatives.
AI-written summary · about
chapters (8)
- 0:00Introduction to obsolescence
- 1:03The journey to leadership
- 5:52Philosophy of becoming obsolete
- 12:50Free jazz leadership style
- 22:10Developing leaders and teams
- 35:45Techniques for sharing knowledge
- 46:51Code review and culture
- 55:05Conclusion and Q&A
related talks
59mThe Tech Lead Elevator: Real Stories and Hard Lessons
18mAgile leadership and technical mastery, a harmonious alliance
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
01h 00mImproving Your Team(work)
23mTech leadership for everyone
50mDistributed Leadership
01h 00mBeyond the innovator’s dilemma
01h 03mBeyond the innovator’s dilemma