One thing that I think gets lost in this conversation is the 0x engineer. I've met a few people who I'd put into this category and I've definitely met people who think of themselves in the 10x mold who I'd categorize as 0x. Ironically in my experience 0x engineers tend to be really good programmers, but they just don't know how to understand or don't care at a deep level what the business wants so they just build whatever is convenient or enjoyable for them to build.They get away with this on poorly managed projects led by non technical people. Eventually, deep into the project the non technical people start to figure out that the thing they are getting is going to be really poorly suited to their needs and by that time they are over commited and totally screwed. Zero or negative value could be delivered over an extended period of time here.
Compared to the 0x developer, a junior developer who gets a basic understanding of what is needed then solved it with a standard well suited tool is an infiniteX developer.
And there is a huge space in the middle here. But I'd venture a guess that all said and done, deeply understanding the problem space and client or business needs correlates more highly with total productivity than programming wizardry over the long run.