March 28, 2026
Code vs. Boss: Choose your fighter
The Case for Becoming an Engineering Manager
From coder to boss: impact dreams vs ‘minions’ nightmares
TLDR: An engineer argues switching to management is about bigger impact and sharper communication, not ladder math. The comments split: some call it AI-padded fluff, others tout mentorship, while veterans say 'no minions' and reformers urge good people to manage to block bad bosses.
An engineer says moving from coding to management isn’t about climbing a ladder—it’s about impact and mastering high-stakes communication. In the piece, they swap “do it my way” blueprints for clear goals, and a teammate returns with something better. The author nods to a popular “don’t be a manager” take, but argues the real choice is which skills you want to build, not who gets paid more. Think: fewer lines of code, more multiplying the team’s output. Read the piece here and the counter-argument here.
Then the comments threw popcorn. One reader rolled their eyes at possible AI padding—“longer but not stronger”—kicking off a side-thread of “did a bot write this?” jokes. Another hailed the missing piece: managers as career guides, not just task bosses. A 30-year veteran dropped a grenade—no “minions,” no chance they’ll be blamed for someone else’s mistakes—earning dozens of “yup” replies. Word nerds piled on the term “individual contributor,” asking how else people contribute, spawning memes and mock job titles. The spiciest camp says some managers are narcissistic power-grabbers, and the only fix is for decent people to step up and manage. The money-and-status crowd counters with flattened ladders and Staff Engineer paychecks. Verdict? It’s impact vs income, mentoring vs migraines, and the thread is still on fire.
Key Points
- •The author transitioned from individual contributor to engineering manager seeking greater impact through team enablement.
- •Anton Zaides’ article arguing against management prompted the author to reassess the decision through a skills-building lens.
- •The author acknowledges management trade-offs: less coding, reduced autonomy, and stepping off a high-demand, well-compensated technical track.
- •Management provided significant skill development, especially in precise communication when others rely on clarity.
- •A practical shift from prescribing solutions to communicating goals led to better team outcomes and highlighted the value of autonomy.