‘Vibe coding’ using LLMs susceptible to most common security flaws
‘Vibe coding’ using LLMs susceptible to most common security flaws
www.scworld.com
‘Vibe coding’ using LLMs susceptible to most common security flaws
16 comments
-
Vibe coding is just like passing all your coding tasks off to that friend who’s been doing coding as a hobby for the last four months.
-
Vibecoding without git (so you can revert back to a last working version) is like:
- Walking into a nightclub without condoms
- Trick bicycling without a seat
- Jumping out of a plane without a reserve chute
- ...
-
In Vibecoding you can let the AI do the git commits and reverts
-
Vibe coding = VaaS, Vulnerabilities as a Service.
-
Who would have thought letting an AI shit out slop code would produce insecure, slop code? I'm shocked, I tell you. Shocked.
-
Just keep giving it more prompts and editing the output until the squiggles go away and it runs. It will be just fine, surely.
-
-
Even classic coders doesn't automatically write safe and secure code.
-
That's the crux of it. People talk like most coders are some kind of know all security and best practices wise.
That's just a lie or virgin innocence.
Most coders are just keyboard monkeys, those are the replaceable ones.
-
-
Lol and hammers are terrible at setting screws. I appreciate the heck out of vibe coding a prototype and massaging it into place. It doesn't work well for security, polish, performance, heck most things really. Vibe coding only really replaced stack overflow lol
16 comments