There are, indeed, technical solutions to social problems

Valorising 'technically effective' over 'socially effective', which is sometimes hidden behind ideas of meritocracy, is a real pain when trying to manage people and coalesce teams to be perform greater than the sum of the parts. The '10x individual' idea is a heinous part of this, too, because it puts lower responsibility to be (or reward for being) a good colleague and team mate on someone who's not good at that, while binding everyone impacted by this individual's choices to a status level where they have to deal with working code now and little-to-no documentation or discussion.

I understand that those things have rare excellent projects started -- but sustained requires collaboration from people co-laboring with you.

One idea with Merge Requests is to set the expectation that a MR which passes the test suite ought to be approved, but you present the changes to the team as a teaching session documenting why you chose the approach and made the MR's design decisions. Because people get better at what they practice doing, you get gains in technical communication ... by practising technical communication.

K3n.