From Developer to Manager... and Back
summary
A developer accepts a hybrid project manager role, discovers management is mostly emails meetings spreadsheets, loses the quick feedback loop of coding, and slides into 10–12 hour days with damaged mental health; a cited study of 53,000 employees, 214 companies (Feb 2018) shows top sellers are likeliest to be promoted, validating the Peter Principle worry. After about one year and three months a role swap and month-long handover returns the person to coding, restoring productivity and job satisfaction.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:45Disclaimer
- 2:53Stereotypes
- 4:37Your pickle
- 6:14The manager
- 7:23Career path
- 8:15The Peter Principle
- 10:00Promotions and the Peter Principle
- 13:41The offer
- 15:18The vision
- 15:59The reality
- 18:57Pyramids
- 20:15Nothing
- 21:31Running to Code
- 21:55Keep Coding
- 23:45Money
- 24:17Motivation
- 25:44Help
- 26:34Project Management
- 27:44The Struggle
- 28:31This is the Time
- 29:07Mental Health
- 30:42Office Zombie
- 32:24The Way Out
- 32:46The Role Swap
- 33:42Stepping Down
- 34:21Back to Coding
- 35:08Takeaways
- 37:17Skype bug
- 38:51Deep dive
- 39:41Appreciation for good managers
- 40:14Wrapping things up
- 41:19Questions
related talks
44mFrom Developer to Manager
32mThe Critical Career Path Conversation
45mFrom Agile coach to manager. And back. Or did I go back
26mSo You Want to Be a Manager? Welcome to Meetings, Metrics, and Mayhem
23mAnd After Developer, Project Manager?
28mIC to manager panel discussion: Bridging the gap going
26mSo you want to be a manager
41mThe Mythical Hands On Manager