> The issue is nobody is spending time in review because the stuff coming out "just works".

People used to be able to write code that was horrible by all the standard metrics but still "just worked" (or at least appeared to). From the stories I've heard, it would get into production all the time, too. But if it's a bigger problem now, then necessarily we know how to fix it, so.

I guess the excitement of the new toy is just leading to some irresponsibility.

I don‘t know that we know how to fix it so well after the fact, but rather we know how to avoid it which is by writing understandable code the first time round.

But we don’t always do that and then things get rewritten and broken etc

Welcome to life in software dev 2026, not so different from 1996