Discussed here a couple of times as well: https://news.ycombinator.com/item?id=37361947 , https://news.ycombinator.com/item?id=43452649
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.
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 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.
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?"