Whats interesting is that this "We don't care about the code, we care about the outcomes" was common management speak for years before AI was on anyone's radar. In some ways it made sense, it was what distinguished your junior programmer from the senior engineer. One worried about the function, the other about how the systems would interact. But it also swept a whole bunch of technical debt and ticking time bombs under the rug. It allowed the ship it quickly and let it be someone elses problem in 2 years when no one can read this garbage, its slow as mud and will require a full rewrite to add one new feature.

AI and its use encouraged use, feels like gasoline poured on that existing mindset.

But with AI debugging and reviewing skills, this could be solved too I believe. It's not going to be write the code and review once anymore. We will run AI multiple passes reviewing it with various perspectives and we would have code as good as any senior engineer can design and build.