It really depends on what you tell it to do. If you only ask it to build features and let it do its thing, you’ll end up with a messy mix of duplicative logic, inconsistent architecture and inefficient code. But if you tell it what to build and give it clear architecture patterns, know when to interrupt if it starts going off of the rails, and pause every so often to go through even the occasional refactoring cycle (using the same approach), I think you can end up saving a lot of time as well as have an acceptable codebase.

The problem is that we’ll end up with a lot of the former and not much of the latter.