I strongly agree that by and large we waste 99% of the compute resources available to us on useless abstractions. However, this is an orthogonal issue to not r

I strongly agree that by and large we waste 99% of the compute resources available to us on useless abstractions. However, this is an orthogonal issue to not reviewing code. To contrast, if we push code to production _before_ review, then production is much more likely to be full of bugs, and we force people to go looking for them afterwards. I've worked in this kind of environment, and the amount of wasted resources (both compute and engineering time) is staggering. Somebody's pet project ends up taking way more compute than anybody would have deemed acceptable and we have exactly the overhead and waste you are referring to. Better, lower overhead abstractions require buy-in, and this means it needs to work for other people than the person who wrote them. At some point it needs review and discussion, otherwise it will just be a continual edit war between competing parties.