Uh...
Uh...
32 comments
-
-
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."
-
Vibecoding:
- go to chatgpt
- ask it to make an app
- ask it to fix errors (ad infinitum)
- ???
- sell app (optional)
- get sued and ruin your reputation (hopefully)
-
The ??? isn’t a reference to underpants gnomes. It’s just that no one has ever gotten LLMs to actually fix its own bugs to find out what that step is
-
Largely accurate apart from special-purpose tools usually being employed instead of ChatGPT
-
Same thing. Coding agents just automate the third step and waste even more money and energy.
-
-
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.
-
It’s using AI to ruin your codebase and build technical debt.
I think it is very funny and fully support companies doing this to themselves.
-
I honestly thought vibe coding was a joke until someone posted a video about it and then realized people were serious.
It's basically the equivalent to your friend who has a brilliant idea for an app and just needs you to do the coding for it - without having any clue how IT actually works.
-
I thought it was a joke until someone at my company gave a company wide presentation on how to use AI to accelerate coding and st several points flat out ADMITTED he didn't know what the hell it was doing but you just need to 'baby sit' it and you get useful scripts out of it. I'm a hardware engineer and I wanted to scream at him.
-
It's not just for coding either. Yesterday, my senior director used Google's AI to ask about the architecture to integrate one of our vendor products with our ERP system (usually my job). Fortunately the AI did me a solid and said "This is a highly complex integration 🤯".
Yeah... No shit, that's why so many of us are employed. Shit's complicated.
-
-
Now, your friend with the birlliant idea doesn't need you anymore and can ask a chatbot to make his brilliant app all by himself!
That is definitely a great benefit of vibe coding: it's an idiot magnet and frees up our brainspace.
-
-
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)
-
Oh is that what it is...
awkwardly zips up pants *
-
vibe coding is very dirty.
-
-
It's going to an llm and typing in the text box "make me an app that does X" then patting yourself on the back for "coding".
-
Have you tried asking Copilot what it is?
-
"Vibe coding" is an informal term, mostly used in online programming communities, that refers to writing code in a relaxed, intuitive, or improvisational way rather than following a strict plan or methodology.
It’s often associated with:
Experimentation → typing out ideas, running them quickly, and adjusting on the fly.
Flow state → coding while listening to music, late at night, or just for fun without rigid structure.
Prioritizing creativity over rules → not worrying too much about best practices, efficiency, or readability at first—just "feeling out" the solution.
Playfulness → sometimes it means coding with minimal context, like making something cool without knowing exactly how it’ll end up.
Some people use “vibe coding” positively (as in getting into the zone and letting intuition guide you), while others use it humorously or critically (as in writing spaghetti code without much forethought).
Would you like me to give you some examples of how vibe coding looks in practice—like snippets that show the contrast between "structured coding" vs. "vibe coding"?
-
-
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.
-
-
-
Remember when that chess champion accused that other chess champion of cheating? It's like that.
-
Unless you're insinuating that using AI to vibe code is like sticking a vibrating dildo up your own ass just to "win" (and then get accused of cheating), then no... it's not at all like that, lol
-
32 comments
When you go to the ER & just start vibe-coding so now the nurses have to debug you.
/s