You must log in or register to comment.
I remember when the term was first coined and it meant something like “asking an llm to code and NOT attempting to validate, fix or correct the outputs yourself. Just keep prompting in natural language until it works.” It was supposed to be a joke - this sort of use hits a wall pretty quickly and illustrates how limited llms can be.
The term has taken off and its meaning is now in flux. I did find it particularly amusing seeing all the LinkedIn lunatics start posting LLM written garbage about “integrating vibe coding Into your workflow” because they thought it was the new buzz word… and I guess they were right.
Prompt an LLM to write a bit of code that does something. Do this 9000 times until it spits out something that vaguely accomplishes this task. You can’t push any of the fever dream nonsense it created into the main branch until you check it thoroughly. In the end you spend more time with this process than you would have if you’d just written it yourself.
The C suite and the board members continue jerking each other off as they call this “efficiency.”
If you need a quick&dirty piece of code, you can generate it by firing some prompts into an LLM. You can get a decent result if you know what you are doing. It may not be production-ready, but often it’s a good starting point. This is NOT vibe coding.
Vibe coding is what people who don’t know what they are doing do when they try the process above, and think it’s production-ready.
Wikipedia defines it as
Advocates of vibe coding say that it allows even amateur programmers to produce software without the extensive training and skills required for software engineering.
Now if you replace some words you see how absolutely bonkers the idea in general is:
Advocates of aircraft autopilots say that it allows even amateur pilots to fly large airplanes without the extensive training and skills required for commercial pilots.
Mhhhh Yes and no
Should vibe coding be used in critical infrastructure. Hell nah
But could I could not care less if someone vibecodes a game or the one millionth second brain productivity app.
Neither do vibe coders.
Original definition: using AI to create a small bespoke kinda-crap-but-it-works apps or games for personal use. It’s a shitty proto but it’s interesting.
(My reaction: ooo not my jam but that sounds neat I guess)
Modern definition: it’s a multi-quadrispillion dollar industry and it’s the future according to some very important board members.
(My reaction: …capitalism ruins fucking everything)
Its a way to imagine you don’t need a developer.
Is that “A1” coding for companies now?
I thought that guy AL Jippity was just doing a ton of work. Like a 10,000x dev.
It’s what in about 2 years, will allow hackers to drain your back accounts through an obvious security flaw in your banking app
What if I told you that with our advanced security AI agent we can scan your code and … Wait sorry, we just got hacked, nvm.
“Our AI security reviews 20,000 configurations every hour. Your money is safer than - shit. Well, nevermind. There’s no money left. Excuse me, I need to leave the country.”
We replaces our entire app with an AI agent, so it can never get hacked!
Oh wait, people just ask it to roll play they are the bank owner and need funds from other accounts?
Who could have possibly predicted something like this? Sam said this AGI was flawless
Oh is that what it is…
* awkwardly zips up pants *
vibe coding is very dirty.
Wait. it’s not a new dating buzzword invented by VICE to generate click baits?
I doubt it.
deleted by creator
It’s a great thing to point idea guys towards so they don’t waste your time.
When you go to the ER & just start vibe-coding so now the nurses have to debug you.
/s
It’s using tools like Claude or other agentic AI to collaboratively make an app. It’s a fun novelty until you realize people paid more than you are doing it without knowing what they’re doing and getting away with it.
