Why It’s Good to Be A Software Manager
summary
Becoming a technical manager does not mean stopping coding; hands-on work continues while owning architecture and roadmap decisions, using Jira or a simple spreadsheet backlog with t-shirt sizing and a clear definition of done. Concrete example: a weekend hackathon closes 2,000 old bugs by writing cleanup scripts implemented in Lua and Go, a move that leads to adopting Lua more widely. Managers gain influence over tech choices (C++20 adoption), commercial exposure, stronger communication, and must handle hard conversations directly, fairly and respectfully.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:42WHY THIS TALK?
- 1:24WILL I HAVE TO STOP CODING?
- 3:51WHAT DO I DO DAY-TO-DAY?
- 7:08HOW DO I MOTIVATE OTHERS?
- 12:46CONCERN 4: HARD CONVERSATIONS
- 14:09WHAT ARE THE BENEFITS?
- 17:22CONCLUSION
related talks
39mTo be or not to be a manager in 2020
26mSo you want to be a manager
01h 01mHabits of a Highly Effective Technical Manager
01h 07mAsk the Expert: Q&A with Engineering Managers
21mShould I become a manager in IT
01h 01mBecoming an Engineering Manager Without Losing Your Technical Soul
56mThe Care and Feeding of Software Engineers
41mThe Mythical Hands On Manager