It's not about "how ugly the code is". Poor solutions heaped on top of poor solutions can result in a system with real users and intractable issues. I'm all for AI, but not reviewing the code seems likely to cause issues long term.

Well, I used to pay more attention to the code, and then I found that if I spent more tokens having the AI review its work than actually creating new features, I was able to get more, better work done.

The AI review stage is where I've found prompting matters a lot more than that initial prototyping phase. I've iterated on prompts and tooling that help the AI keep the codebase clean-ish.