The post was probably made by a troll, but the comment section is wise to the issue.
I know we like to mock vibe coder because they can be naive, but many are aware that they are testing a concept and usually a very simple one. Would you rather have them test it with vibe coding or sit you down every afternoon for a week trying to explain how it's not quite what they wanted?
Consulting opportunity: clean up your vibe-coding projects and get them to production.
Its just funny that it ends up costing more time
Whoa whoa, what do you want to do, crash the entire US stock market over here?! Our whole economy is propped up by the story that AI is the future and will replace all jobs forever. We've got MS paying OpenAI paying Nvidia, and that's making the line go up.
So let's be cool with throwing around "numbers" that "prove" the emperor has no clothes. Because, like, we gotta pretend he does at least until the next thing that needs every video card ever.
Back in my day, we called that pseudocode. It's code-like, but not in any actual programming language that you could compile from.
It's more of a set of ideas of how to accomplish something, than it is actually coding.
The fun part is, that pseudo code can be adapted to any actual programming language.
Idk why everyone is crazy about vibes all of a sudden.... But sure.
I just use it to whip up a mockup, like a GUI with certain usability features. I'm the one who has to work with highly specific, proprietary software and usability is total ass. But it's difficult to put this into words that the dev is willing to read through. So I'd rather show it. But that's about it.
Bruh yer not doing it right. Are you stupid, bruh? You gotta work on yer promps, bruh. You gotta watch some tiktoks on it, bruh. Bruh, go watch @demisets4, bruh. Learn to prompt, bruh. Your not good at it, bruh. Bruh, you should try something else if you can't figure it out that's a you problem, bruh.
is it not making someone fix generated project is a massive work rather than building smething from the ground up?
I had a project where I was supposed to clean up a generated 3D model. It has messed up topology, some missing parts, unintelligible shapes. It made me depressed cleaning it up.
few of them was simple enough for me to rebuild the mesh from the ground up following the shape, as if I'm retopologizing. But the more complex ones have that unintelligible shapes that I can't figure what that is or the flow of the topology.
If I was given more time & pay I could rebuild all of that my own way so I understand every vertices exist in the meshes. But oh well that contradicts their need of quick & cheap.
Can someone tell me what vibe coding is?
From what I understand, it's using an LLM for coding, but taken to an extreme. Like, a regular programmer might use an LLM to help them with something, but they'll read through the code the LLM produces, make sure they understand it, tweak it wherever it's necessary, etc. A vibe coder might not even be a programmer, they just get the LLM to generate some code and they run the code to see if it does what they want. If it doesn't, they talk to the LLM some more and generate some more code. At no point do they actually read through the code and try to understand it. They just run the program and see if it does what they want.
Simply not caring and letting the dice roll machine drive
There are a bunch of tools that are basically a text editor hooked up to an LLM. So you use natural language to prompt the software to write code for you.
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
