[phplovesong]

The fact that i hear this mantra over and over again:

"She wrote a thing in a day that would have taken me a month"

This scares me. A lot.

I never found the coding part to be a bottle neck, but the issues arise after the damn thing is in prod. If i work on something big (that will take me a month) thats going to be anywhere from (im winging these numbers) 10K LOC to 25K LOC).

If thats a bechmark for me the next guy using AI will spew out at a bare minimun double the amount of code, and in many cases 3x-4x.

The surface area for bugs are just vastly bigger, and fixing these bugs will eventually take more time than you "won" using AI in the first place.

[thisissomething]

It really depends on how you use it. I really like using AI for prototyping new ideas (it can run on the background while I work on the main project) and for getting the boring grunt work (such as creating CRUD endpoints on a RESTful API) out of the way. Leaving me more time to focus on the code that really is challenging and need a deeper understanding of the business or the system as a whole.

[phplovesong]

The boring stuff like crud always needs design. Else you end up with a 2006 era PHP-like "this is a rest api" spaghetti monster. The fact that AI cant do this (and probably never will) is just another showstopper.

I tried AI, but the code it produces (on a higher level) is of really poor quality. Refactoring this is a HUGE PITA.

[mmcnl]

I think it's strange too. Why is Lord of the Rings such a famous book series? Surely not because Tolkien could write faster than others.