Many years ago, I worked at a company with a product that ran on Mac and Windows. The Mac version was pretty solid, but the Windows version had some problems.
They had a talented team of developers who were mostly Mac experts and just starting to get a grip on Windows.
I was known at the time as a "Windows expert", so they hired me to help the team get the Windows version into shape.
My typical day started with "house calls". People would ping me with their Windows questions and I'd go door to door to help solve them - and to make sure they understood how to do things on Windows.
In the afternoon, I would work on my own code, but I told everyone they could always call on me for help with a Windows problem, any time of day.
One colleague asked me: "Mike, how can you afford to be so generous with your time?"
Then in a performance review, I got this feedback:
"Mike, we're worried. Your productivity has been OK lately, but not great. And it's surprising, because the productivity of the rest of the team has improved a lot during this time."
I bit my tongue, but in retrospect I should have said:
"Isn't that what you hired me for?"
Reminds me of this post: https://dannorth.net/blog/the-worst-programmer/
Discussed here a couple of times as well: https://news.ycombinator.com/item?id=37361947 , https://news.ycombinator.com/item?id=43452649
I got an HR meeting a couple of years back where they selected me to be laid off because I wasn't closing as many tickets off as the rest of the team. Every single ticket had been through another engineer first and they had failed to resolve it.
I was absolutely fine with this and didn't defend it because the enhanced payment I was going to get was huge. But alas they worked it out in the end and here I am fixing arcane shit still that no one else has a clue about or is defeated by.
I knew a person like you, two decades ago, in a laptop repair facility (my boss).
He was hired full-time (at like 4x my hourly rate) simply because he was the last person working there familiar with how the DOS-only headless terminals were installed (simple, but vital infrastructure). I didn't even understand what he was doing, but knew if I learned it I would have a lifetime solid-six-figure tech support job (two decades ago).
Bossman mostly just sat around and played WoW (seriously, half his hours "on the clock," waiting for next disaster)... but whenever a smug new vendor came in pedaling latest & greatest... he was often the saver of many times his salary. Nobody really liked him (I did — we'd smoke weed together and attend irregular heavy metal shows), but everybody knew he was important technically (e.g. no purchase orders could go through without his machine upkeep — multimillion dollar budgets).
People would literally turn away from him in the hallways so-as to not attract his comicbookguy inquisitions — particularly if you were a network troublemaker / idiot.
I miss his expertise / guidance / wisdom. Favorite bossman ever.
I can be found around heavy metal shows as well hahaha.
I try not to be comic book guy these days. I was in the past. I just want to learn together with people. That is all.
so they kept you aroumd then, eh? sounds like someone in HR with half a brain actually looked at the cost per ticket. those type of escalation tickets are ~3x more costly to resolve than non escalations. sounds like the total $$ per day of your tickets was higher than all your teammates.
I would prefer to have someone with a full brain in HR.
Open a ticket for that ... ?
Hahahaha. Depressing but funny.
Great story, and I feel it! A lot of companies, when they hire a senior person, say they want you to be a "force multiplier" but when you actually go and multiply your team's force, they turn around and say "bbbbuut, wait--your individual performance...."
Sounds like the person doing the performance review just relies on metrics. Sounds like a shitty leader.
Not only that, but that person was relying on a totally incorrect metric in the first place. Tale as old as time.
This is why data driven decision making is a trap. Even if the data is correct, which it's usually not, its still not complete just by definition. It's instinctually a dumbed down, distilled, and one-dimensional view of the real world, of meat space, and you gotta treat it like that.
Here's what is scary. I have been looking at many job descriptions for a Developer Experience Engineer or similar positions. About half of them ask for experience with automated tools to measure developer productivity!
Many such cases.
I always wonder how productivity is measured
Vibe Managing has long preceded Vibe Coding.
1000% vibes in most tech orgs
Poorly.
Easy, telemetry to count the number of mouse clicks when working.
The #1 skill good devs need to develop is self-marketing. Would that all managers could recognize talent by output alone but alas we all know that's not the case.
It is sad when the people who are in charge can't recognize such an important role. I'm so sorry this happened to you, and if you can, keep mentoring. At a time when juniors are struggling more than in the past you could be the one to really help.