The Mythical Hands On Manager
summary
Argues that being a coding manager is a different career not a promotion and becomes untenable once a team grows — expectation: when a team reaches about four people a manager can’t reliably ship code and grow people. Uses examples from Glide (built a wrist‑cam band, shipped late), OrCam and Chegg, core Bluetooth experience, and a startup that hit “millions of users.” Recommends clarifying expectations, companies avoid hires to kill two birds with one stone, and suggests keeping skills by keeping hands warm with code review, architecture and non‑critical tasks.
AI-written summary · about
chapters (12)
- 0:00Introduction and audience
- 5:11Speaker background
- 6:48Entering the tech industry
- 10:00First steps in management
- 14:24The reality of team lead
- 17:06Defining management
- 21:03Choosing the management track
- 24:36Hands-on management
- 28:37Key considerations for managers
- 33:31Maintaining technical skills
- 35:48Conclusion and summary
- 36:56Q&A session
related talks
26mSo you want to be a manager
51mTeaching and managing for technologists
19mWhy It’s Good to Be A Software Manager
44mFrom Developer to Manager
32mThe Critical Career Path Conversation
48mFrom Developer to Manager... and Back
01h 07mAsk the Expert: Q&A with Engineering Managers
01h 01mHabits of a Highly Effective Technical Manager