The concept of the 10x programmer seems to have been drifted from its original meaning. It isn't that there's a coder that is 10x better than a good coder. It is that a lot of people are really bad at their jobs, and a coder that thinks and learns about problems can be far better than those people. It comes from terrible "corporate drone" software developers in the 80s and 90s - the ones that would takes weeks to dev…
> It comes from terrible "corporate drone" software developers in the 80s and 90s - the ones that would takes weeks to developer simple routines. Ironically, a lot of the 0.1X engineers I've worked with in the 2010s were the most technically competent. Obsession with cutting-edge tools and being technically correct over shipping quickly can sink a person's productivity. They're the people leading the charge to rewrit…
From HN comments, I get the impression that this is a common problem at companies like Uber. Lots of smart engineers with great technical talent, but they spend all their time making pet apps and services which satiate their interest in and excitement towards programming/engineering, but which have not much direct relation to the actual product or any other ultimate business objectives. If there is any relation, it's indirection upon indirection. I imagine this is probably because the core product is so narrowly-focused and basically "done" that they have to look for any other way to spend their time and energy without getting bored and demotivated.
I would guess this happens at a lot of companies with single, simple (from the user's perspective), narrowly-focused products, like Twitter.