Acquiring knowledge that nobody else has in more than one critical system isn't necessarily a 10x engineer, more like an engineer who is critical to the busines

Acquiring knowledge that nobody else has in more than one critical system isn't necessarily a 10x engineer, more like an engineer who is critical to the business in (up to) 10 different systems or intersections of system. Management should try to minimize situations where only one person knows how to operate critical systems (see the character Brent in "The Phoenix Project") but that's not what I understand 10x to be. To me (as a developer), a 10x is someone who eats, breathes, and sleeps nothing but the job and can literally crank out 10x the lines of code. Whether other can maintain or understand that code is one problem with having a single person outperform their peers by so much; it also means that if management doesn't recognize this as an aberration then when that person hits the lottery/gets a better offer/gets bored and quits/is hit by a bus you're in a position of trying to explain to senior management why you're going to need to hire five people to replace the one 10x person. This isn't to crap on the raw ability and talent of a 10x -- I'm massively envious of that ability! -- only to point out that with disproportionate output comes consequences.