Dave’s fingers were hovering over his mechanical keyboard, but for the first time in 6 years, they weren’t moving in that rhythmic, percussive dance of a man who knew exactly where every semicolon belonged. Instead, he was staring at a calendar invite for a ‘Conflict Resolution’ workshop. There was a thin layer of cold sweat on his neck. He had spent 46 minutes trying to figure out how to tell Sarah that her pull requests were becoming a liability without making her cry. In his previous life, three months ago, he would have just refactored the code himself in 6 minutes and moved on. But now, Dave was a Manager. He had been promoted because he was the most brilliant engineer in the building, a move that made perfect sense to the executive board and absolutely zero sense to the laws of human psychology.

We have this pathological obsession with the vertical climb. We assume that because someone is a virtuoso at a specific task, they must possess the innate desire to oversee others performing that same task. It’s the Peter Principle in its most distilled, corrosive form. We systematically promote people until they reach their level of incompetence, and then we leave them there to rot, wondering why the department’s productivity has dropped by 26 percent since the ‘star’ took the helm. It’s a tragic waste of talent. We take a person who was providing 136 percent of their expected value in a technical capacity and transform them into a manager who provides 46 percent of the required leadership value.

The Ghost Coder and the Bottleneck

Dave doesn’t want to be in that meeting. He wants to be in the IDE. He spent last night-from 11:06 PM until nearly 3:46 AM-secretly rewriting the backend logic for the new module because he couldn’t stand how the junior devs were handling the API calls. He didn’t tell anyone. He’s a ‘ghost coder’ now, a manager who performs his team’s jobs in the shadows because he doesn’t have the vocabulary or the temperament to coach them into doing it better. He thinks he’s helping. In reality, he’s creating a bottleneck that will eventually choke the entire project.

I remember talking to Natasha P. about this last week. She’s a virtual background designer too, but she focuses on high-end corporate aesthetics-the kind of backgrounds that make a cubicle in Scranton look like a penthouse in Dubai. She told me she once had a client who was a world-class surgeon promoted to Head of Hospital Administration. The man was miserable. He kept trying to scrub into surgeries he wasn’t scheduled for because the spreadsheets were making his soul itch. We do this in every industry. We take the creators and turn them into curators, then act surprised when the gallery goes stale.

The Contradiction of Value

There’s a strange contradiction in how we value skill. We claim to prize expertise, yet our only way of rewarding it is to move the expert away from the very thing they are an expert in. If you’re the best at $676-an-hour work, we ‘reward’ you by making you do $46-an-hour administrative tasks. It’s a backwards logic that treats management not as a distinct, difficult skill set, but as a generic prize for seniority.

“

I’ve made this mistake myself, honestly. I once tried to hire an assistant to handle my client communications so I could focus on the design work. I picked the person who had the best eye for color, thinking their aesthetic alignment would make them a great proxy. It was a disaster. They were a brilliant artist, but they couldn’t organize a grocery list, let alone a project timeline. I spent more time fixing their emails than I did designing. I had to let them go, which felt like firing a part of my own creative brain. It’s a messy realization when you realize that ‘good at thing A’ has zero correlation with ‘good at managing people who do thing A.’

This creates a permanent ceiling on what an organization can achieve. When your leadership layer is comprised of reluctant engineers or frustrated artists, the culture becomes one of avoidance. Difficult conversations are skipped. Long-term strategy is sacrificed for short-term technical fixes. The team becomes demoralized because they can feel their manager’s resentment, even if it’s masked by a polite Zoom background.

The Logic of Material Hierarchy

We need to start looking at roles as specific functions rather than rungs on a ladder. There is a profound logic to the way we structure our physical spaces that we fail to apply to our human hierarchies. When you’re designing a room, you don’t use a floor tile as a ceiling beam just because it was the ‘best’ tile in the showroom. You look for specific acoustic properties, for the way a material absorbs the chaos of a room, much like how Slat Solution focuses on the marriage of aesthetic and function. You choose the material that fits the purpose. If you need sound dampening and a clean, modern look, you use an acoustic slat wall; you don’t just stack more bricks because bricks are ‘senior’ to wood.

Why don’t we do this with Dave? If Dave is a 10x developer, why isn’t there a career path that pays him like a VP but lets him stay in the code? Why must he be forced to navigate the treacherous waters of 360-degree feedback loops and quarterly budget reviews? We are burning our best assets to light a fire that doesn’t even keep the room warm.

Maintenance Over Power

The coffee grounds are finally out of my keyboard. It took 26 minutes of meticulous picking, but the keys click properly again. It’s a small victory, but it’s a reminder that maintenance is about precision, not power. If I had tried to clean this keyboard by shaking it violently or hitting it with a hammer (the management equivalent of a ‘motivational’ speech), I would have just broken the mechanism.

We have to stop treating management as the only destination for talent. We have to start respecting the individual contributor enough to let them remain an individual. Until we do, we will continue to have organizations filled with 466 different versions of Dave, all of them staring at Jira boards they hate, secretly wishing they could just go back to the semicolons.

The Cost of Learned Helplessness

What happens to a team when their leader is a ghost? They stop growing. They wait for Dave to fix it. They lose their own sense of agency because they know, at the end of the day, the ‘expert’ will just come in at midnight and overwrite their work anyway. It’s a cycle of learned helplessness that starts at the top and trickles down until the whole company is just one guy working 96 hours a week while everyone else watches YouTube.

I’m going to send Dave a message. Not about work, but about a new mechanical keyboard I think he’d like. It’s a small thing, a gesture to the version of him that still exists under the ill-fitting suit of a manager. Maybe if we all start recognizing the ‘Daves’ in our lives for what they actually are-and what they aren’t-we can stop breaking our best people in the name of progress.

Most of the time, the answer to whether the title bump is worth the 6 hours of meetings every single day is a quiet, desperate no.