In fairness, you could throw the most senior engineer into a brand new codebase, and they would probably make a dozen mistakes if you immediately had them pick up invasive and risky work.
Teaching is a lot like (a certain style of) management. You learn what motivates someone, make the connection between that and the subject matter at hand, and make it accessible for them to get to the next level. The rest takes care of itself.
History bears out that cheap and satisficing soundly beats expensive and optimal every time. Until we have smarter and more prescient decision makers in leadership, the bottleneck on output will be the quality of decision making not the quality of code. Trying more things faster and cheaper will win.
If it were really groundbreaking, I imagine it wouldn't have burned out after a little missed hype. See No Man's Sky.
The other way to look at this is, thank goodness we didn't waste months or years on a failed game concept. Instead we got to market and validated (or invalidated) the concept fast.
Marketing, networking, and sales are the job. Or a large part of it. If you don't have connections, knowing how to make connections is part of it.
Accept that there are other skills besides engineering, and they can be just as challenging to learn, and just as opaque from the outside of you don't understand it.
I'd be wary of testing this as binary. It's not self centered versus not. It's a continuum, which I think you understand because you discuss making progress.
But, what you don't seem to acknowledge is that you don't hear what you don't hear. Some groups may be quietly judging you in a way that is VERY difficult to perceive because you don't understand their subtle social cues. Or, maybe you have perfect social awareness in all situations. I truly don't know.
The problem with the latter has always been the same. It requires careful review to ensure that system boundaries aren't being crossed. It's very obvious if your repo sounds to access to a new database. Less so if it imports a function directly from an inappropriate package.
It's always been like this, just on a smaller scale. Every time you join a group, some people can read the room, learning and sensing the cultural implications, while others step in all the landmines and don't even hear the explosions. How do you do this? Not sure how to explain it, mostly calibration through experience!