If vibe coding is a programming paradigm, then so is vim.
Return oriented programming is not a…
…you know what, never mind. You keep doing it. Cybercrime is cool anyway
In my day vibe coding meant a delivery pizza, loud music, an eighth, and no other plans for the day.
In my days it involved something vibrating and Bluetooth
I’m not sure I even really understand what “vibe coding” even means.
Telling an LLM what you want the program to do and blindly trusting whatever it outputs, basically.
Are serious people really pushing that?
It’s mostly beginners thinking of it as a shortcut to making software without learning any of the underlying theory. Basically, why struggle your way through a Rust tutorial on fighting the borrow checker when you can just get AI to do it? Though the issue is as soon as there’s something too complex for the AI to figure out, you’re out of luck because you’ve been deliberately avoiding learning the necessary concepts to fix it yourself.
As for whether serious people are pushing it, most actual software engineers, not really, but company management would absolutely like nothing more than to replace all their developers with AI, so yes they’re pushing it pretty hard.
It’s the new hyped up version of “no-code” or low-code solutions, but with AI so you have more flexibility to footgun.
Return Oriented Programming is a security exploit not a programming paradigm.
It’s surprise programming.
At the company where I work, in the span of roughly one month, the term vibe coding went from being used exclusively in the derogatory sense to one that is now primarily used in the positive sense. Fuck big tech and fuck capitalism! Fuck all of this shit!!
