Riding the paradox as a lead developer
summary
Leads face concrete trade-offs: keep coding time while running tech lead lunch peer groups, carve out Google-style 20% time for learning, and champion infrastructure work like docker so deployments actually get easier. Use a simple metric rule — never have more than three different ways to solve the same problem — and run weekly catchups as feedback loops to measure whether consistency, delivery and improvement are actually moving together.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:22What is a paradox
- 1:58Staying technical
- 2:59Pressure from business
- 3:53Balancing learning and innovating
- 4:46Maintaining consistency
- 6:12Keeping people focused
- 8:41Business and technical needs
- 10:06Adaptive leadership
- 10:44You arent alone
- 12:46Uncertainty
- 14:26Binary approach
- 15:12Impact
- 16:09Recap
related talks
29mThe Constant Life of a Tech Lead
11mTips on scaling your leadership outside of your comfort zone
36mBecoming a tech lead - Lessons learned
59mThe Tech Lead Elevator: Real Stories and Hard Lessons
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
23mTech leadership for everyone
49mEngineering Leadership in Turbulent Times
50mDistributed Leadership