Developer's guide to selling your soul
summary
Team lead from Radian who builds cloud core banking in Scala lays out 11 lessons aimed at engineers moving into management: the Peter Principle means half of promoted people may be unfit; management equals owning outcomes and always taking responsibility; no democracy beyond tiny teams — final decisions rest with leadership; meetings must yield actionable decisions and aim for roughly eight correct choices out of ten; cultivate learning from mistakes, give frequent specific feedback, set clear goals and visible priorities, and model the behavior you want.
AI-written summary · about
chapters (14)
- 0:00Introduction and disclaimer
- 1:40Eleven lessons on management
- 2:02The no rule in leadership
- 3:28The Peter Principle explained
- 5:14You're no better than anyone
- 5:56Responsibility in leadership
- 8:02Democracy in leadership
- 9:07Make a decision or die trying
- 11:56Clear goals and expectations
- 13:04Mistakes as learning opportunities
- 14:28Feedback is the king
- 16:15Transparency in priorities
- 18:02All eyes on you as a leader
- 20:12Final advice and Q&A
related talks
49mPractical Leadership for Software Developers
33mThe Care and Feeding of Software Engineers
32mThe Care and Feeding of Software Engineers
17mSo You Think You Can Lead a Software Team?
58mHow to survive and thrive as an engineering leader
43mLeading in Tech
19mLeader in the Land of Dilemmas
27mLevelling up as a Lead Developer