A high output team player is gold and we want as many as possible. A high output singleton will likely have sacrificed some element of quality or maintainability or thoroughness or likely even their own personal lives to reach that output, for the projects they enjoy doing.
That output is unlikely to translate into a new, less interesting project and if the work or system is now structured to require that level of output then few would want to take up the position.
The over used canoe metaphor is useful, you want people to pull at the same speed. I also enjoy the 'always be leaving your job' approach that guides people away from building themselves into the system.
- You choose to write grammar school textbooks just so you can hire cheaper writers.
- Or worse, you're required to write grad school textbooks but you still hire cheaper replaceable writers.
We are conflating skill with performance, but the 10x theory (IIRC) is that they are correlated, or at least can be given the proper motivation.
Team players are always better than singletons, so let's assume there's no correlation there (which may be a stretch, sure.)
Someone who doesn’t want to take over someone else’s code deep dive and understand it first is not high performer in my understanding.
Efficient debugging and understanding systems other wrote or created is basic requirement for high performing dev in my opinion.
There's a fundamental difference between being able to rip apart a ball of mud and rebuild something sane out of it and being excited to do that for a pittance.
Let me read between the lines here and assume the worst, then please correct me and tell me it doesn't apply to you.
A left. High performer candidate B didn't want to pick up A's stuff. Let's say it was over-engineered or over-complex or whatever. You ended up hiring C, and C was not a high performer. In fact, a wild guess: you hired two C's at the price of one A.
Perhaps your preference was to hire two "everyone is replaceable" C's all along? That's not to say that some projects are not more suited to low performers. But the engineering management style can tip the scales no matter what.