The Care and Feeding of Software Engineers
summary
After promotion from IC to lead the core claim is: leadership is a muscle that you build by listening, delegating, and protecting your team. A poll of ~5,000 developers says priorities are safe to fail, clear vision, flexibility, and recognition costs nothing. Concrete practices: run one-on-ones and repeat what you heard, stop coding for your team, delegate decisions so the team isn’t bottlenecked, tailor work to personality types, and prioritize quality over velocity while shielding developers from meeting overload.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:08From coder to team leader
- 3:23Building leadership muscles
- 5:12What developers want from leaders
- 8:00Active listening in leadership
- 12:14Recognizing and empowering teams
- 14:54Supporting junior developers
- 16:24Nurturing mid-level developers
- 18:21Managing personality types
- 26:49Handling downhearted team members
- 28:39Dealing with disconnected developers
- 30:49Creating autonomous teams
- 31:58Final advice and Q&A
related talks
33mThe Care and Feeding of Software Engineers
01h 01mThe Care and Feeding of Software Engineers
56mThe Care and Feeding of Software Engineers
10mLeadership in Software Engineering
49mPractical Leadership for Software Developers
26mCare and Feeding of Engineers
17mSo You Think You Can Lead a Software Team?
58mHow to survive and thrive as an engineering leader