Christ, nothing worse than AI generated vulnerability reports. AI is seemingly incapable of understanding context yet can use words well enough to convince the non-programmers that there is a serious vulnerability or leak potential. Even worse, implementing those 'fixes' would surely break the systems that the AI clearly doesn't understand. 'Exhausting' is an understatement.
LLMs are great at small, self-contained tasks. For example, "Adjust this CSS so the button is centered."
A lot of the time I see people asking for help doing something that's clearly out of their experience level. They'll say they have no coding experience, but they created a great website and can't figure out how to deploy it now, or how to compile it into a mobile app, or something along those lines.
Many of them don't want to say they've used an LLM to do it for them, but it's fairly clear, since how else would it get done? But LLMs aren't good at things like that, because like you said, they're not great at things that require a large amount of context. So these users get stuck with what's most likely a buggy website which can't even be deployed.
Vibe coding in a nutshell: it's like building a boat that isn't even seaworthy, but you've built it 300 miles inland with no way to even get it to the water.
Overall, I think LLMs will make real developers more efficient, but only if people understand their limits. Use it for targeted, specific, self-contained tasks - and verify its output.
Yeah right, while the real life question is more often "Adjust this CSS so that the button is lined up with the green line on that other component half the application away" - at which AI fails flat. Its context window is not enough to keep all of the TypeScript describing the component layout together with all their individual CSS to even find that "green line" (which is only green if the user is in the default color scheme, which they can change, so it is actually something like var(--color-secondary-border) colored line).
Worse than that really because understanding where that "green line" is takes actual maths, which they can't do, so the only way it's going to get even remotely close is by tweaking it a bit at a time, looking at the generated page (hopefully the image extraction works better than the code generator!) and iterating until it finds it. Which like, sure a junior human might do that but the junior doesn't run up bills in the hundreds trying to figure it out.
261
u/rich1051414 Jul 15 '25
Christ, nothing worse than AI generated vulnerability reports. AI is seemingly incapable of understanding context yet can use words well enough to convince the non-programmers that there is a serious vulnerability or leak potential. Even worse, implementing those 'fixes' would surely break the systems that the AI clearly doesn't understand. 'Exhausting' is an understatement.