How to survive and thrive as an engineering leader
summary
Former superstar developer must stop equating value with commits and learn to measure impact by team and product outcomes: spends far more time on meetings, hiring (about 20 roles in one effort), coaching, vendor management and writing business cases for a legacy refactor that initially fails without nontechnical buy‑in. Practical tactics include seek first to understand responsibilities and leadership style, schedule regular “balcony time” for reflection, translate technical choices into business metrics (uptime, velocity, defect rate), and bring solutions not problems to empower teams.
AI-written summary · about
chapters (7)
- 0:00Start
- 9:49Seek first to understand
- 19:35Be consistently learning
- 22:57Lead by example
- 38:51Leadership defined
- 45:04Some commonly asked questions
- 58:12Ted Talks on Leadership
related talks
45mHaving impact as an Engineering Manager
29mHow to Become a Great Engineering Manager
49mEngineering Leadership in Turbulent Times
31mFrom Engineer to Engineering Manager
16mFrom Leading to Lagging How to Stay Relevant?
38mWho is a Lead Engineer today
58mMy Journey to Understanding Technical Leadership
31mImproving engineering effectiveness: A journey for the entire organization