You are incorrect. In my 18 years in dev, I've seen quite a few of those fabled 10x or 100x devs, and oh boy they can deliver if unconstrained by processes and

You are incorrect. In my 18 years in dev, I've seen quite a few of those fabled 10x or 100x devs, and oh boy they can deliver if unconstrained by processes and bureaucracy. Rest of the team then scrambles to figure out how things work once they move on to next cool thing. Always some cool new framework (or even better, one developed just for this situation because its fun). All of them, no exception, loved exploring another framework du jour (and java has/had tons of those) for each project. None of them were 'finishers' - ideal for them would be prototype something quickly, and then move on, daily project grind was universally hated. Few had to be treated like babies by managers - finding new topics hey can play with to maximize contribution to the project (which often paid off, ie once we got 10x throughput increase compared to default ActiveMQ installation, the guy did some proper debugging/perf testing only possible due to open source nature of the product... brilliant guy, but hardly a team player, complicated personality).