A lot of companies chase highly skilled, creative, motivated developers and then stick them with routine, grindy jobs until they quit or lose the will to live. It doesn't matter how sharp your scalpel is if they're being wasted maintaining some enterprise CRUD app.
Case in point, I have a nice Japanese knife set. My chef's knife (your scalpel) sucks at cutting bread compared to the set's serrated bread slicing knife.
Both of those knives such at spreading peanut butter and jelly to make a sandwich.
The right tool (or person) for the job is what matters.
For example, I know someone who insists on having the exact same chair, screen, keyboard, mouse, and IDE at every job. I believe he's been called arrogant for that. But his explanation was that all of that is necessary to make past muscle memory translate. Like this, he can type fully blind at an impressive speed and navigate every project purely with shortcuts.
If thinking is not your bottleneck, then it makes a lot of sense to optimize for typing speed.
You might be right. But I spent 23 years in industry and can think of just a couple people who I might consider to be 10xers... and that's not enough to build all the software that has to be built in the world.
>To the outside, them enforcing a productive environment might look like diva behavior.
Your examples of chairs, screens, etc - I don't have any beef with that; that's not what I mean by prima donna behavior. What I've tended to see are people who definitely are not 10xers who have somehow got the organization in a stranglehold of toxicity.
Try arguing at FAANG that you'll need your own quiet office for your stuff plus a window and some potted plants to help you stay awake and concentrate. I think you'd be thrown out for "refusing to be a team player".
And yes, in my 18 years in IT I have also met toxic hostage keepers. But my impression was that those were people who were highly skilled and have in-depth knowledge of the system. And then somewhere along the way they had a fallout with management and wanted to leave, but the company couldn't hire any suitable replacement. So now both company and employee are stuck in an abusive relationship, for fear of being alone otherwise.
Somewhere over the past few years, I came to peace with this point. Because production software tends to be really gross, for complicated but legitimate reasons. In fact, I think the beauty is in keeping something that looks really mangled operating with any degree of success - that is in fact the mark of a successful and functional team, if they are able to keep it all working with any degree of sanity.
This is not to say that your second point, about bare minimum level of skill necessary, isn't also incredibly valid. But, I don't blame this on individual workers, but rather on the system (IE: don't hate the player, hate the game). Incentives are to make your money in a phase of the moon and move on. Incentives are to move up or out. Incentives are not to build quality, but to build good enough. So long as that's how the incentives are structured, it's how the game is going to go.
...and that's not a 10x developer, because if your limiting factor is how fast you can type and how often you can navigate shortcuts, you're a keyboard monkey, not a software developer.
Just think of the ongoing operational headache from all the code someone would generate if they were typing non-stop, as fast as they could, all day. Even if it is really good code, if you need that much code, you're already screwed.
The 10x doesn't come from typing more and generating more code. It comes from all the typing you don't do.
If typing is your bottleneck, then it makes sense you aren't putting a lot of thought in to what you are doing.
I have also met people who write overly complicated and lengthy code, but that doesn't mean everyone does.
The rails app that he built for my employer is still in production use 5 years later and it has turned out to be well organized and easy to maintain.
If typing is your bottleneck, then you're either careless and overly verbose... or you are insanely knowledgeable about what you do.
But really most people are working for a business not research. And in such cases the productivity could be measured in affect say revenue or profit. That's hard to measure for a lot of things.
And it takes teamwork, and a lot of human factors.
I doubt typing speed really comes into it. If you can do 40wpm or more it's fine IMO. Hunt and peck is OK.
An "idiot" using NodeJS writing it all in one big ugly index.js file might make the company a million with an idea or subtle change that the Linux Kernel genius missed.
Not really sure how you measure 10x.
The only way to do it is to confine what it means. "Can they implement this given problem in 1 hour? Then they are 10x"
But... software by it's nature is about implementing problems that are even hard to define in the first place and spotting opportunities. The right decisions - what NOT to develop, or what tech to use could make such a big difference. It might be hidden in an inane looking decision to use C# for example, that doesn't make you "look" like a 10xer.
I "10x" was originally intended as a hypothetical talking point.
There probably are 10x people in a team. The 10x status could change rapidly as circumstances change, team dynamics and company goals change. Someone else might take the invisible 10x crown once they get to work on a project that aligns with their strengths.
At any time you don't know who to 10x is. You need some system to decide what is a fair salary and who you want to try hard to keep. A good manager should have a feel for who that is in their team. If that person moves into another company they may not be that person anymore in the new team.
So 10x probably exists (as defined as ratio of best to worse). If it didn't exist it means that most people are pretty much performing the same, which I don't believe. But I doubt anyone is permanently a 10x contributor, and I doubt many people (include the 10x-er themselves) can tell who it is.
I believe that's due to being curious and slightly introverted when young, so these people just have lots and lots of experience. Such people could be manufactured by training them on many different programming disciplines over many years. It's just that for almost any company, investing so much into training is not feasible. That employee might leave once training is over.
On the other hand, if you don't have the organizational support - which often isn't about budget so much as actual verbal, emotional, political, psychological kinds of support - then your productivity will likely be very low. When I've been in places with management or clients that were repressive in their behaviors, well... they reaped what they sowed and out the door I went asap. Normally someone will pop up and say something about the risks or the security or something driving that kind of behavior or process - yes, I've worked in some high-risk environments, but there is a difference between a process designed to minimize faults and one that is just repressive because of ignorance, egos, etc. If you treat people badly, they will not produce at a high level.
There are unique individuals like this, but I've noticed that the ones I've seen in the wild... this wasn't their first time building such a system. In another thread today someone was talking about building video conferencing systems and someone said "it's only easy for you because you've been doing it for years!" If it's the third time you've built that particular kind of subsystem, chances are you've made a lot of mistakes and know what you are doing, and now you can make it look easy.
This is not to say that there aren't some who are more talented than others, but as another poster in this thread noted - it's more like a 90/10 or 80/20 split, where we could get rid of a big chunk of people who just aren't qualified.
There are mechanics that can build a car from scratch, and even forge the spanners they use from iron ore, all without reading a manual. But do you need that person to service your car.
I don't disagree with this, but I also came to the conclusion that it is just raging against the machine to think that it is fixable. So long as there is money to be made, no barriers to entry, and no economic incentive to improve the situation, it will only continue to get worse. I'm of the same opinion now that I was in the 90s - the fix is to mature the discipline to a true profession of licensed, qualified, software engineers. But, it's a pipe dream to think that will ever happen in a meaningful way.