Tech leadership, one year after
summary
Company-scale move from 100 to 300 engineers forces concrete changes: set a target of deploy 10 times a day, introduce RFCs to democratize architecture, run company-wide public post-mortems after incidents, and ship a volunteer-built safer continuous-deployment system from a hackathon that actually reduces release friction. Operational specifics include biweekly one-on-ones, blind performance reviews tied to a career ladder, PR templates that populate git blame context, and communication headers to mark action required.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 2:35Tech lead role explained
- 8:05Balancing vision and failure
- 20:58People management and feedback
- 31:48Performance reviews and growth
- 42:33Handling conflicts and transparency
- 53:00Key takeaways and book recommendations
- 54:13Q&A session
