The Tech Lead Elevator: Real Stories and Hard Lessons
summary
Starts from concrete lessons: copied or AI‑generated code becomes yours and must be owned and maintained; a timezone library example asks whether to spend two senior devs six months or accept simpler tradeoffs — context decides; a Cordova e‑learning app ships and works but becomes unmaintainable; reports require six‑seven back‑and‑forth iterations until a two‑hour joint meeting fixes them; a notification bug turns out to be a deleted config, not code; poor docs cost six hours and MySQL 5.7 lingering adds €2,000/month. Principle: question assumptions and bring people together.
AI-written summary · about
chapters (12)
- 0:00Tech lead lessons from 20 years
- 1:39Senior dev vs tech lead
- 2:02First code review responsibility
- 9:06Time zones library investment
- 14:07Challenging artificial requirements
- 21:12Fixing broken reports
- 26:53Debugging notification failure
- 32:57Documentation in tech decisions
- 37:34Knowing your tools
- 45:43Balancing tech debt and upgrades
- 52:34Caring for your team
- 58:35Summary
related talks
52mThe Tech Lead Elevator: True stories and hard lessons
29mThe Constant Life of a Tech Lead
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
30mWhat I wish I knew as a first time Tech Lead
36mBecoming a tech lead - Lessons learned
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
47m"Talking with Tech Leads"