Lessons from a lifetime of doing, teaching, managing, and leading technical development
summary
Compresses 50+ years into practical lessons: change is constant, manage it with incremental, auditable steps, and prioritize people over tools. Uses concrete examples — rewrites a messy bridge simulator in Python and finishes it in a weekend, pioneers test-first habits (tests-before-code traced to 1971), and builds an audit system that helps win a Yahoo Japan antitrust case and preserves roughly $10B revenue. Recommends team sizes of about six to twelve, warns of a single-person “bus number,” and shows productivity falls past ~60 hours/week.
AI-written summary · about
chapters (13)
- 0:00Introduction and theme
- 1:08Change is the only constant
- 4:26A lifetime timeline
- 9:49Career choices and luck
- 13:29Hardware to software shift
- 15:57Discovering Python
- 21:21Managing knowledge workers
- 26:45Managing risks in projects
- 30:41Structure and chaos balance
- 36:29Learning from experience
- 39:18Team size and productivity
- 44:21Hands-on management
- 46:33Q&A session
related talks
30mLessons Learned: A Developer's Perspective on Teaching & Learning
22mNotes to my younger self
28mLessons and Expierience from 15 years of Agile Coaching
28mLessons learned after more than 20 years working in IT
51mTeaching and managing for technologists
49mPractical Leadership for Software Developers
58mBackwards Compatible- Lessons from a Quarter Century in Software
27mTell Us Another Story Grandpa: Lessons Learned over 16 Years as a Developer