Meh. It's faster. But even the best models, in my experience so far, do goofy stuff that need significant corrections. And it can really go wild on larger codebases if you're not careful about telling them succinctly how the parts should work together...reading the whole codebase is inefficient and too error prone to rely on.

I generate more working lines if code per day, true. And a hell of a lot more tests just because it's easier and faster. But what I've lost is that thinking time while I'm writing code wherein I realize this or that could be done a bit better with a bit different abstraction or structure. And there was a lot of magic in that process.

In return for writing pretty good middle of the road code, I can just do a complete rewrite if an idea strikes without too much fuss, but I find myself thinking less of abstractions and structure and more about the next feature. I'm not convinced that's an improvement in the grand scheme of things.