Introduction: An Unfiltered, Player-Centric View of Management
How do you all think about the career path to management? Writing code as an engineer is fun, but once you reach a certain level of seniority, you often find yourself at a crossroads: to shift to the “management side” or not. It’s a tale as old as time.
Recently, looking for some hints to clear up this ambiguity, I picked up “The Software Developer’s Career Handbook”.
Since the first edition is a bit old, it’s debatable how perfectly it applies to today’s modern, agile development processes. I skipped parts like recruiting and job hunting that aren’t immediately relevant to me right now. However, the later sections detailing “how to maneuver as an engineer” and “the struggles of a manager leading a team” absolutely hit home.
The appeal of this book isn’t in its polished business theories or “societal common sense.” Instead, it is brutally articulated from the perspective of an individual player who has tasted the mud on the front lines. It bluntly confronts the subtle discomforts you feel daily, and things you thought you understood but actually haven’t been practicing.
To ensure I don’t just close the book thinking “that was a good read,” I’m organizing the topics that resonated with me as a reminder for my future self.
The Irreversible Shift to Manager and the 3 Roles
In the IT industry, almost all managers are former engineers. But the skill of “building good things quickly” cultivated during your engineering days is not enough to manage. The rules of the game change completely—from a job where you build things with your own hands, to a job dealing with humans, an endlessly incomprehensible and complex entity.
The book points out that managers have three roles, ordered by difficulty:
- Coach: Someone who imparts their experience and wisdom. However, being too well-liked carries the risk of making it hard to deliver harsh truths.
- Fixer: In abnormal situations, they ignore bureaucratic procedures and go all-in to solve problems. While reliable, if a manager solves problems too quickly, it can make subordinates acutely aware of their “failure,” which ironically risks destroying team morale.
- Leader: They set the direction everyone should head in and make the hard choices. A leader provides respectful and thorough guidance, but if things still don’t work out, they are the only ones who can make the painful decision to remove someone from the team.
Identifying “Organic” vs “Mechanical” Bosses
It seems managers broadly fall into two types. This point was extremely relatable.
- Organic Manager: Values emotions and what they see and hear. They deeply understand the personalities of their members and highly value 1-on-1s. Knowing that illogical human elements affect work, they try to create a fun meeting atmosphere where everyone feels comfortable speaking up.
- Mechanical Manager: The geek type who tries to understand the world through “structure.” Operating on mental flowcharts, they prioritize predictability and visible facts. They prefer meetings that strictly stick to the agenda and finish precisely on time.
One isn’t necessarily better than the other; what matters is how you maneuver around them. Organic bosses will adapt to your flexible thinking, but mechanical bosses despise ad-hoc changes. Therefore, you need tricks like handling a mechanical boss by giving them a detailed schedule beforehand and communicating strictly according to it. Simple, but life-saving knowledge.
Filtering Information: The Standard for Reporting
Bosses harbor two contradictory desires: “I want my subordinates to handle everything on their own” and “I want them to report everything to me.” If you actually report everything, you’ll simply overflow your boss’s brain buffer. We have to appropriately filter information down to “things only I can tell them.”
When in doubt about reporting, evaluate against these criteria:
- Is this within my scope, and can I handle it alone?
- Is it a massive company-wide issue like HR or a scandal? (This is an immediate report level).
- Is this a problem the boss is likely interested in? (Neglecting their interests will make them worry and turn into a micro-manager).
- What are the exact merits of solving it alone vs the demerits of failing?
This filtering ability is precisely the survival skill that bridges the gap between the front lines and management.
Meeting Formats and How to Maneuver
The observations on daily meetings were also quite painfully accurate. By observing what kind of meetings your boss voluntarily hosts, you can accurately gauge what type of information they crave.
- Technical Meetings: Hosted by bosses who still have lingering attachments to tech and want to remain engineers. You should report technical details.
- Status Coordination Meetings: Hosted by PM-minded bosses who want to ensure everyone is marching toward the same goal. You should report on overall project progress.
3 MTG Patterns to Create “Margin” in the Team
To provide a team with a sense of security and the “margin for free-thinking,” the book suggests mechanically and precisely repeating a set pattern of boring meetings. It introduces these three:
- Manager Dialog (Monday Morning): A time to relax and breathe, where the boss casually asks what’s on your mind.
- Team Meeting (Post-dialog, 2 hours): Shifting from grasping the situation to “proposing solutions.” You discuss three things: measurable progress, this week’s tactics, and long-term strategy.
- Retrospective Meeting (Friday 4 PM): No new agendas are set here. You simply verify if the tactics decided on Monday were actually executed.
By sticking to this rhythm, you prevent unnecessary chaos.
Slicing the Team into “3 Functions”
Another interesting concept for healthy product development involves drawing three circles on a whiteboard, assigning each role to a different person, and letting them negotiate with healthy tension.
- Bit (Development): The technical leader who pushes actual product creation and makes critical tech decisions.
- Feature (PM): The role that aggressively demands feature enrichment for the customer, ignoring cost or time.
- Truth (Program Manager): The custodian of truth who grasps diverse internal information, neutralizes schedules, and translates departmental dialects.
These three parties represent the front line, the customer, and the schedule constraints, respectively. By arguing as equals, an unbiased, superior product is more likely to be born. Better than playing nice in a buddy-buddy club.
Human Behavior Under Stress and Trouble
Personally, the most fascinating and painfully resonant section was the raw depiction of human behavior under stress. Because we engineers try to perceive things as “predictable systems,” we are creatures prone to panic when faced with unexpected bad news (system collapse).
Humans unconsciously show initial “fight” or “flight” reactions to unexpected events. These are merely reptilian brain defenses and shouldn’t be judged as good or bad.
- Saying No / Getting Angry (Fight): A reaction to protect oneself. Since anger inflicts psychological harm on others, you must quickly contain it and steer toward resolution.
- The Quiet Ones (Appears like flight, but isn’t always): A mix of competent “true quiet ones” simulating worst-case scenarios in their heads, and “fakes” who have simply lost their minds. For the fakes, you must prompt them to speak to organize their thoughts.
- Asking Questions (Constructive): Relentlessly asking why it happened. This allows for early, forward-looking responses.
- Taking Action / Hoarding Blame (Flight): Some will aggressively start doing meaningless work out of panic, while others will waste energy blaming themselves for everything.
- Threatening to Quit! (Flight/Fight): A geek-specific reaction where they freeze in despair. Give them a minor distraction task to help them regain their faculties.
The trick to surviving team warfare is not to react emotionally to these initial outbursts, but to listen quietly until they are calm enough to grasp the facts, and then offer an “escape route.”
Bosses Turn into Micro-Managers During Trouble
Under the intense stress of a major incident, even normally calm bosses transform.
- The Questioner / The Prioritizer: Driven by anxiety, they shower you with questions, demand perfect ToDo lists, and order re-dos over the slightest lack of info.
- The Confused / The Enemy: Bosses who change priorities every few hours, or worse, lash out and attack subordinates out of anger.
These are temporary metamorphoses brought on by pressure. As a subordinate, your job is to calmly explain detailed countermeasures and deadlines, providing the comfort needed to return them to their “normal, mild-mannered self.”
The 3 Waves of Resignations in a Company Crisis
The account of information transmission and talent drain when a company heads toward bankruptcy is chillingly real. Inside a company, there are two communication channels: the logical “strategic conversation” by executives, and the “tactical conversation” by the general staff.
- 1st Wave (Strategic Exodus): The excellent managers who know what’s coming next are the first to flee. An interesting point: observing which department people vanish from lets you guess the root cause—sales issue or product issue.
- 2nd Wave (Tactical Exodus): Seeing the executives move, the people on the ground panic. Lacking concrete info, irrational witch hunts and conspiracy theories begin, leading to a chain reaction of resignations out of fear. This inflicts the most massive damage on the company.
- 3rd Wave (Aftermath and Headhunting): A wave that hits when it’s already too late. Former colleagues who jumped ship early to stable environments start reaching out to exhausted insiders left behind, kicking off aggressive headhunting.
It’s an absolutely perfect model of organizational collapse.
Demo Presentations and Not Hiding Ideas
For an engineer, a demo presentation or a meeting isn’t just a sales pitch; it’s a “conversation to discuss your idea with others and find ways to improve it.”
When you hit upon a brilliant idea, hiding it because of overlapping personal evaluation goals is a terrible move. Ideas only improve when subjected to many eyes. By letting others find the flaws you missed and filling them one by one, you build rock-solid confidence. Hiding things only distances you from the true goal of “creating a product that wows users.”
And at any demo, “persons of interest” who dominate the room’s atmosphere will inevitably show up.
- The Silent Type: Prepare massive amounts of detailed background material just for them. Keep your pace by breaking your talk into small chunks and asking “are we clear up to here?”
- The Aggressive Type: Passionate critics. Even if they poke you with “I don’t really get it,” don’t panic or get angry. Use it as a trigger for dialogue by asking exactly what part is unclear.
- The Bossy Type: The one who demands, “Skip the background and just show me the working thing.” When this happens, be ready to jump straight into the demo.
A powerful technique was introduced to reclaim hijacked momentum: insert an unnaturally long “complete silence” of 15 seconds after a Q&A session. Alternatively, deliberately slow down the tempo of your core pitch to half-speed (since adrenaline tends to make you talk fast). This sounds highly effective.
Gamification and the Utility of “Problematic People”
Finally, leveraging an engineer’s true nature to build culture.
We engineers are creatures of “systems thinking” who believe the world can be controlled by finite rules, which means we naturally love games. Transforming a hopeless task like bug fixing into a “Whiteboard Game” was a fascinating idea. Score 10 points for finding the root cause, 10 for solving it, and compete within the team.
Crucially, you must establish clear, inviolable rules. And most importantly, “do not use money as a reward.” Money is a stressor that strains relationships. Instead, providing a non-monetary visual trophy—like a tiny plastic statue of a rhino you can show off on your desk—is far more effective.
Also, we shouldn’t forget the existence of the “problematic person” who is incompatible with team culture. They destroy teamwork with unpredictable behavior. But while the company might loathe them, their unorthodox claims and strategies often prove to be wildly correct in hindsight. As a “catalyst to break the shell” that prevents the company from stagnating in one direction and destroys existing culture for the sake of the future, they are actually indispensable.
Conclusion: Survival Strategies for Tomorrow
Organizing this all out, I realize how much “survival maneuvering” I had subconsciously ignored in my daily work. This book is not a clean, theory-armed management textbook; it’s a raw survival guide narrated from the perspective of a mud-covered player.
“Productivity scales exponentially if you use the right tools.”
True to this quote, I want to master the tools that fit me best. Even if I can’t do everything perfectly, I want to start implementing things one by one—like filtering reports to my boss, using the 15-second silence on bossy reviewers, and reassessing my favorite tools.
