They're trying to normalize calling vibe coding a "programming paradigm," don't let them.
They're trying to normalize calling vibe coding a "programming paradigm," don't let them.
We've seen functional programming, now get ready for dysfunctional programming
AKA whenever I write something in a strictly functional-only language and think I'm ready but I'm just way too used to object oriented to get it.
Not my old ass over here cheering for functional coding… nope…
… but yep.
Love functional coding. Depending on the use case it works really well.
Wonder what return based is, sounds similar to functional.
Less of a paradigm but a way to write exploits but still more of a paradigm than vibe coding. It basically means "hey I can buffer overflow over the return address, let's treat the program's code as a VM to do what I want".
At first I thought "vibe-coding" was just writing code that felt useful at the time without having like design documents or a formal plan. Literally just coding based on vibes. And I thought it was nice that they finally recognized the way I have been writing code for the past ten years when all my bosses and managers haven't.
Imagine my disappointment when it turned out to be what it actually is.
vibe coding (derogative)