The Care and Feeding of Software Engineers
summary
Companies promote excellent coders into managers with no training and lose people as a result; concrete fixes include asking teams what they want, making the team safe to fail and advocating for salaries, running one-on-ones, and having juniors speak first in standups so fresh ideas surface. Role-specific actions: demo and pair for juniors, pairing and confidence-building for mid levels, give seniors autonomous projects plus teaching duties. Also tailor care to personalities—introvert, extrovert, pessimist, optimist—and delegate and empower consistently.
AI-written summary · about
chapters (22)
- 0:00Introduction by host
- 1:49Why engineers leave companies
- 3:36Human skills gap in leadership
- 8:12Mid-level developer comfort zone
- 11:45Promotion to leadership role
- 15:40Leadership as a learned muscle
- 19:14Safe to fail and try new things
- 23:08Respecting team differences
- 27:20Recognition over compensation
- 28:47The art of delegation
- 31:59Unique team member needs
- 33:23Caring for junior developers
- 34:04Supporting mid-level developers
- 35:26Empowering senior developers
- 36:32Team psychology basics
- 44:37Handling down-hearted team members
- 46:23Building autonomous teams
- 47:28Call to action and summary
- 48:49Q&A: When to move on
- 50:56Q&A: Bad leader in charge
- 52:44Q&A: Mentors vs managers
- 54:30Q&A: Karaoke moment
related talks
33mThe Care and Feeding of Software Engineers
01h 01mThe Care and Feeding of Software Engineers
32mThe Care and Feeding of Software Engineers
26mCare and Feeding of Engineers
01h 07mAsk the Expert: Q&A with Engineering Managers
19mWhy It’s Good to Be A Software Manager
21mHow to grow your engineers into great leaders
26mSo you want to be a manager
