Doubt is a cold, metallic taste at four in the morning, especially when you are staring at a cursor that hasn’t moved for 29 minutes because you are no longer allowed to touch the keys. Mark is sitting in the fluorescent hum of a quiet office, his fingers hovering over a mechanical keyboard he bought back when his job was to solve problems instead of ‘facilitating’ them. He’s the best engineer I ever hired, and right now, he’s probably the most miserable human being in a 49-mile radius. He was promoted to Engineering Manager 119 days ago, and in that time, he has written exactly zero lines of production code, but he has attended 349 meetings that could have been summarized in a single, well-formatted email. We did this to him. We took our finest instrument and used it to hammer a nail into a block of gelatin, then wondered why the nail didn’t hold and the instrument got sticky.

🛑 The Ultimate Logical Fallacy

I’m writing this while still nursing the bruises from an argument I lost yesterday. I was right, by the way. I told them the server architecture wouldn’t handle the 209-percent spike in traffic we see during the holiday season, but I was overruled by a ‘Director of Strategy’ who hasn’t seen a terminal window since 2009. It’s that same kind of institutional arrogance that leads us to believe that excellence is a liquid you can just pour from one container into another without losing a drop. We see a brilliant coder and think, ‘He’s so good at his job, he should teach others to do it.’ It’s the ultimate logical fallacy of the modern corporate structure. It’s like watching a world-class sprinter and deciding the best way to reward her is to make her the head of the logistics department for a shoe manufacturer. You lose the speed, and you gain a very frustrated person who just wants to run.

Finley F. knows all about this kind of structural failure. Finley is a car crash test coordinator, a man whose entire professional existence is dedicated to finding the exact moment when a beautiful piece of engineering becomes a heap of twisted scrap. He once told me that the most dangerous part of a car isn’t the engine that’s too powerful, but the bracket that’s too weak to hold it. ‘You can have a $99999 engine,’ Finley said, wiping a smudge of simulated blood off a crash dummy’s forehead, ‘but if the mounting bolts weren’t designed for that torque, the whole thing is just a very expensive projectile.’ Mark is that engine. He has the torque. He has the power. But the ‘manager’ bracket we’ve bolted him into wasn’t designed for a human being who derives his dopamine from logic gates and elegant algorithms.

The Clash of Disciplines

If you stay an individual contributor for too long, people start to look at you like you’re stagnant, like you’re a piece of fruit that refused to ripen. So, we push. We nudge. We offer the ‘opportunity.’ Mark took it because he thought it was what he was supposed to do. He thought it meant he would have more influence over the product he loved. Instead, he found himself in a world of 1-on-1s where he has to manage the emotional fallout of a junior dev’s breakup, and budget reviews where he has to justify why the team needs a $499 monitor when a cheaper one ‘works just as well.’ He is navigating the messy, irrational, contradictory world of human emotions using a brain that is hard-wired for the binary clarity of C++.

It’s a different profession. That’s the part we miss. Management is not ‘Level 2’ of Engineering. It’s a completely different game with a different set of rules, physics, and win conditions. In engineering, if something breaks, there is a reason. There is a log file. There is a stack trace. In management, if someone breaks, they might not even know why themselves. You can’t ‘debug’ a person who is feeling undervalued, and you certainly can’t optimize a team’s performance by tweaking their ‘source code.’ It requires empathy, patience, and a high tolerance for ambiguity-traits that are often diametrically opposed to the precision required to be a top-tier engineer. I’ve seen this play out 19 times in the last decade, and it always ends the same way: with a resignation letter and a hole in the team that takes 9 months to fill.

Functional Design vs. Misapplied Authority

We need to start looking at our teams like we look at architecture. You don’t take the master carpenter who can feel the grain of the wood and make him the foreman of a 49-story skyscraper project just because he’s ‘the best.’ You keep him on the wood. You pay him more. You give him the title of Master, not Manager. In the world of design and physical space, this is why people choose a Slat Solution for their environments; they understand that the material has a specific purpose. You don’t ask the acoustic paneling to hold up the roof, and you don’t ask the load-bearing beams to provide the sound dampening. Every element has its function, and when you confuse those functions, the whole room feels wrong. The acoustics are off, the structure is compromised, and the people inside are uncomfortable.

💡 The 19 Minutes of Self

Finley F. would look at Mark’s current calendar and see a car that’s been driven into a wall at 69 miles per hour just to see how the upholstery holds up. It’s a waste of the upholstery and a waste of the car. Mark spent 9 hours yesterday trying to resolve a conflict between two developers about a naming convention. By the time he got home, he was too drained to even talk to his wife. He sat in the dark, and eventually, he opened his laptop. He found a bug that had been bothering the team for 39 days. He fixed it in 19 minutes. For those 19 minutes, he felt like himself again. He felt the rush of the logic, the satisfaction of the ‘success’ message. Then he realized it was 2 AM, and he had a 9 AM meeting to discuss the Q3 roadmap. He deleted the fix. He didn’t want to explain why he was still working on code when his job was ‘strategy.’

The Obsession with ‘Up’

I should have fought harder when they suggested the promotion. I should have pointed out that losing Mark as an engineer would set the project back 149 days. But I was tired of the argument, the same way I’m tired of the argument about the server racks. We have this obsession with ‘growth’ that only moves in one direction. We think that if you aren’t moving up, you’re sliding down. We don’t value the depth of expertise as much as we value the breadth of authority. It’s a mistake that costs us billions in lost productivity and even more in lost human potential. We are training our best people to leave us because we won’t let them do the things they are best at. If we keep this up, we’ll end up with a company full of mediocre managers who used to be extraordinary creators.

Data After the Impact

I’ll tell him that it’s okay to want to go back. I’ll tell him that the world needs his code more than it needs his presence in another ‘sync’ meeting. […] Otherwise, we’re just building rooms where the sound has nowhere to go but to bounce back and deafen us all.