codingdave
10 days ago
It isn't 10% less quality. It is more like 90% less quality. It does great at basic coding, but still royally sucks at system design. It codes itself into corners that need to be completely refactored. It picks the first path it sees that works, even if there are better solutions, because it doesn't understand what is available as built-in features of different tech stacks and platform. Or, to be more accurate, it doesn't understanding a single thing it is saying, so has zero thought to put into what is actually the correct solution. My favorite one is when it delivered a DB schema to me that re-invented auto-incrementing fields by creating new stored procedures and triggers... for IDs that weren't even auto-incremented.
So I feel just fine. I use AI when it helps, I do the work myself when it doesn't. All you need to do is learn which is which.
codegeek
7 days ago
"It is more like 90% less quality."
Depends on who is doing the work. If you are a junior who doesn't have any fundamentals and/or started career after 2022+, I wouldn't trust the AI code. However, if you were already a senior/experienced architect, AI is superpower.
throwaw12
10 days ago
> It is more like 90% less quality
Which tool are you using and whats your tech-stack? my experience is not same as your in terms of quality, our stack is primarily Java
> It codes itself into corners that need to be completely refactored
This part is important, if you give full autonomy indeed code becomes mess, but then there are 2 aspects to it: (1) so what? it becomes mess, anyway is code read by agents and written by agents these days (not fully, but a lot). (2) eventually things get complex very quickly, that you wont be able to build mental models about the project, because it wasnt written by you, which forces you to use agents even more, leading to almost complete autonomy, at some point, you wouldn't understand the code anyways.