>
Therefore, as the company sees it, they deserve the bulk of the rewards since they are (magnanimously) giving the opportunity to the 10x engineer.I think it's really two things.
1. The company provides the structure in which the engineer works. Code is not valuable on its own, it's valuable when it solves a business problem. The company structure converts business problems to engineering problems for the engineer to solve. That transmogrification has value and the ability to build & maintain the transmogrifier (aka the rest of the company) is a skill that gets rewarded. The transmogrifier also uses money as one of its inputs (salaries for the rest of the company) and so some of the "pure value" that the engineer creates can't be converted directly to money for the engineer, because it has to be used in the "business problem to engineering problem" conversion process.
It's similar to the argument about taxes. Why should I pay taxes for things I don't use? Well, even if I don't drive, the roads support other parts of society that benefit me.
2. The engineer effectively pays the company (meaning the owners or shareholders of the company) to reduce the engineer's risk. If an engineer wants to extract every cent of value they create then they need to also take the burden of all the risk. Otherwise the company owners will not make enough on the successes to cover the failures.