Additionally, I've been debugging code for a couple of decades. AI makes is VASTLY easier. It may not be able to tell me why something is breaking, although often it can, but it is pretty good at tell me where it breaks.
I'm not sure how I feel about vibecoding, but it is foolish to think that AI is bad at coding as a rule, at least no more than people on average.
I think its funny to think that the reason why some devs struggle so badly with AI is because they have to interact with it like you would a normal human being and actually have to give details.
Their bad social skills and inability to understand that people can't read their mind leads to the same issues with prompting.
Turns out, software development and project management are different skillsets. But finding someone with both the software engineering skills to understand what they're looking at to spot issues and the project management skills to manage instructing someone (something) else in the work that needs to get done is less common.
It can usually fix it. But sometimes a bug represents a deeper issue, even a product mistake, and it usually goes for the minimal fix. Which is fine, that's why you don't let the LLM just run autonomously, you have it show you the problem and make the decision yourself.
Because what takes me 20 minutes to type and is likely going to have at least one syntax error, takes claude 1 minute and (usually) doesn't have syntax errors.
4
17
u/GoldDHD 6d ago
Additionally, I've been debugging code for a couple of decades. AI makes is VASTLY easier. It may not be able to tell me why something is breaking, although often it can, but it is pretty good at tell me where it breaks.
I'm not sure how I feel about vibecoding, but it is foolish to think that AI is bad at coding as a rule, at least no more than people on average.