I personally know people who can do in a day what a "regular" programmers won't be able to do at all, no matter the timeframe. I also know people who can crank out a couple of KLOCs of pristine, nontrivial C++ a day, every day, with ease (whereas a "regular programmer" does like 20, if you average it out).
If you were asked to do a postmortem on that, would you be insisting that the skill level and productivity of the programmers involved was "meaningless" to the outcome? Not even address it in the report?
Are you going to hire someone who is 4'11" and never played basketball before in the NBA? Are you going to hire a janitor to lead your space program? All so you can say that your qualified employees are infinitely better? That's ludicrous but exactly what you're suggesting.
No I don't. I said technically ambitious startup because I didn't mean a scenario where the group was too clueless to even program something easy. Read my comment assuming the programmers in that startup scenario are average industry programmers. Does your answer change?
You can see 10x or 100x developers only when you have large complex problems that could take years to solve correctly by a regular developer (e.g. scalable load balancers, scalable messaging systems, decentralized trading engines, advanced ERP systems, scalable machine learning solutions). Some of these projects can and do take years to implement, but a 10x developer can deliver in 1/10th of the time.
For example, from my own personal experience, I worked and maintained a popular open source project for 5 years (part time), but I rewrote the whole thing (to the same standard as before in terms of meeting functional requirements/stability) in just 3 months (part time); that's 20x productivity.
The irony of 20x productivity is that during the rewrite, there are times when I would sit a whole day without implementing a single line of code; just thinking and searching for the best solution to a tiny sub-problem that had significant implications for future sub-problems. So the productivity gains were not a result of faster coding; it was the result of being able to foresee future problems and considering all possible alternatives and possible permutations of design decisions.
Here is an example anecdote of what it means when people talk about 10x programmer. Here the "hero" of the story was infinitely more productive than everybody on the team.
Henry Ford had ordered a dynamo for one of his plants. The dynamo didn't work, and not even the manufacturers could figure out why. A Ford employee told his boss that von Neumann was "the smartest man in America," so Ford called von Neumann and asked him to come out and take a look at the dynamo. Von Neumann came, looked at the schematics, walked around the dynamo, then took out a pencil. He marked a line on the outside casing and said, "If you'll go in and cut the coil here, the dynamo will work fine." They cut the coil, and the dynamo did work fine. Ford then told von Neumann to send him a bill for the work. Von Neumann sent Ford a bill for $5,000. Ford was astounded - $5,000 was a lot in the 1950s - and asked von Neumann for an itemised account. Here's what he submitted: Drawing a line with the pencil: $ 1 Knowing where to draw the line with the pencil: $4,999 Ford paid the bill.
If you have a group with a very low productivity as average, then a single very good developer can be a 10x developer compared to that group. From the perspective of one of the 1/5 developers this senior “2x average” dev will look like the unicorn 10x dev. Perhaps this is where the myth comes from?
Have some humility and accept that there are people out there who are immensely more gifted than you are.
Aggressive mediocrity is distasteful.