Yeah if you just let it run wild, it will produce subpar results. But that is not much different from humans tbh.
When you discuss design and architecture first, and write that out in a design doc or something along those lines, it works quite well for the most part.
And 9 out of 10 times when it produces some poor results, just asking "is this really a good approach?" or just stating "This code makes me very sad" it will most of the time do a really good job of analysing why that code is bad and how to improve it.
I was talking about style and architecture. In all these cases the code is working as intended either way. There is no such thing as "correct" style and architecture. There are only tradeoffs. You should know that if you have 31 years of experience.
> There is no such thing as "correct" style and architecture. You should know that if you have 31 years of experience.
And you should know that this is not accurate. But at this point this has devolved into a dick measuring contest, which I refuse to do. Have a good day.