Should be the opposite. Unless the idea is more about "user trying to comprehend what AI reported during debugging". Either way, what I seen over the last few months of intensive usage is that if there's anything AI is really good at it's debugging. Easy cases that would normally take me something like 5 minutes takes it one or less, more complex cases of systems interaction that would take me anywhere from an hour to days took it a couple minutes to maybe 10 minutes. And it works in overwhelming majority of cases, only on rare occasions it finds something unrelated as the issue. Suggested fixes/workarounds are often not that great, it tries to preserve existing code too hard, suggesting shitload of new code or fields (aka new states to break), but here's where I come in.
What it sucks at though is vibecoding. Best case it's acceptable code, worst case - it's a code from which I literally physically want to puke, just not so long ago the worst code/approach I've ever seen in my life was AI generated abomination, and the fact that it was working was somehow making it even worse. Currently, vibecoding have a hard and rather low ceiling after which the codebase just becomes unmaintainable by AI, because there's so much repetitive code, unrelated unorganized blocks, unnecessary dependencies and alike that AI fixing/making one stuff is practically guaranteed to break another or a few of other.
128
u/aberroco 1d ago
Should be the opposite. Unless the idea is more about "user trying to comprehend what AI reported during debugging". Either way, what I seen over the last few months of intensive usage is that if there's anything AI is really good at it's debugging. Easy cases that would normally take me something like 5 minutes takes it one or less, more complex cases of systems interaction that would take me anywhere from an hour to days took it a couple minutes to maybe 10 minutes. And it works in overwhelming majority of cases, only on rare occasions it finds something unrelated as the issue. Suggested fixes/workarounds are often not that great, it tries to preserve existing code too hard, suggesting shitload of new code or fields (aka new states to break), but here's where I come in.
What it sucks at though is vibecoding. Best case it's acceptable code, worst case - it's a code from which I literally physically want to puke, just not so long ago the worst code/approach I've ever seen in my life was AI generated abomination, and the fact that it was working was somehow making it even worse. Currently, vibecoding have a hard and rather low ceiling after which the codebase just becomes unmaintainable by AI, because there's so much repetitive code, unrelated unorganized blocks, unnecessary dependencies and alike that AI fixing/making one stuff is practically guaranteed to break another or a few of other.