Leadership for Developers
summary
Claims include that leadership’s goal is to empower teammates to be effective for the business, backed by a Google study naming psychological safety the top predictor of team effectiveness. A 15‑year framework contrasts individual contributor, manager, and leader‑of‑leaders roles, notes teams of up to 100, and cites building Sass Haml and an early mobile Wikipedia site. Practical prescriptions: say I don’t know, model vulnerability, give direct feedback, treat promotion paths as reversible, and read Culture Code for more.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:30Overview
- 4:21Whats the goal
- 6:24Do a good job
- 10:57Leader of leaders
- 14:59How to know if youre doing a good job
- 17:17Vulnerability
- 19:43You dont know
- 24:18Feedback
- 26:52Trust
- 28:43Indirect Outputs
- 29:52Burnout
- 32:37Core Value
- 33:22Fun
- 33:59Questions
- 34:57Ageism
- 37:32Books
- 38:20Favorite Part
- 39:48Asking for Promotion
- 41:25Risk
- 43:57Tech Lead vs Manager
- 45:10Sensitive Employees
related talks
32mDesigning Leadership Growth in Tech Teams (When Developers Just Want to Code)
10mLeadership in Software Engineering
30mDeveloper First – A New Leadership Mindset
28mShared Leadership – leaders, leaders everywhere?
47mLeading in Tech
46mEssentials for Building and Leading Highly Effective Development Teams
59mTaking Lead
32mThe Care and Feeding of Software Engineers