

Consider: the facts
People are very bad at judging their own productivity, and AI consistently makes devs feel like they are working faster, while in fact slowing them down.
I’ve experienced it myself - it feels fucking great to prompt a skeleton and have something brand new up and running in under an hour. The good chemicals come flooding in because I’m doing something new and interesting.
Then I need to take a scalpel to a hundred scattered lines to get CI to pass. Then I need to write tests that actually test functionality. Then I start extending things and realize the implementation is too rigid and I need to change the architecture.
It is as this point that I admit to myself that going in intentionally with a plan and building it myself the slow way would have saved all that pain and probably got the final product shipped sooner, even if the prototype was shipped later.

The end of your comment was
Which is a general statement and not dealing with your specific circumstance. If a tool works for you, by all means keep using it.
However, broadly across software that is not the case. So the “productivity and quality debates” are not ridiculous … the data supports the sceptics.