First Steps as a Lead
summary
Becoming a lead starts with a concrete plan: a three-month transition with an assigned mentor, a department-created step‑by‑step process and early pairing that shifts to pair programming then code reviews. Surprises include heavy meeting load and a career switch away from coding. Practices that matter: regular one‑on‑ones, health check meetings, giving feedback immediately tied to the event, balancing positive and constructive comments, and keeping development feedback separate from performance reviews to shorten the long feedback loop.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:21First Learning
- 3:07Leadership
- 4:00Meetings
- 4:55Career switch
- 5:45Learning new skills
- 7:23Earning trust
- 8:54Solving problems
- 9:35Feedback loop
- 10:52Taking decisions
- 13:03Summary
related talks
29mLeading Leads - Lessons from a growing team
37mFrom Developer to Lead
16mLead Dev, 3 Years of Experience, So What?
36mBecoming a tech lead - Lessons learned
50mMaking the Leap to Tech Lead
46mLearning to Lead a Craft Team: Year One.
17mSo You Think You Can Lead a Software Team?
43mHow to Lead? Testimonial of a Lead Android Engineer