Vibe coding is useful for super basic bash scripting and that’s about it. Even that it will mess up but usually in a suler easily fixed way
A buddy of mine is into vibe coding, but he actually does know how to code as well. He will reiterate through the code with the llm until he thinks it will work. I can believe it saves time, but you still have to know what you are doing.
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.
Consulting opportunity: clean up your vibe-coding projects and get them to production.
That comes up in that sub occasionally and people offer it as a service. It’s 2 different universes in there - people who are like giving a child a Harry Potter toy wand that think they’re magic, and then a stage magician with 20 years of experience doing up close slight-of-hand magic that takes work to learn, telling the kid “you’re not doing what you think you’re doing here” and then the kid starts to cry and their friends come over and try to berate the stage magician and shout that he’s wrong because Hagrid said Harry’s a wizard and if you have the plastic wand that goes “bbbring!” you’re Harry Potter.
AI used extremely sparingly is sometimes helpful to an experienced coder. “ChatGPT, generate a set of unit tests for this function.” Okay, some of these are dumb, but it’s easier getting started on this mess than just looking at a blank buffer. Helps get the juices flowing a bit. But man, you try to actually do anything with it, and suddenly you’re lost chasing a will-o’-wisp.
Oh man, I love ChatGPT for one thing in particular: “Hey chatbot, is there some library or standard library function for that very specific, yet still kinda generic thing I’m trying to do, so that I don’t have to write it myself?”
It does frequently give a helpful answer. That is, it doesn’t give me working code, but a helpful pointer to some manual where I can find good instructions for how to use the thing to solve my problem.
I don’t want to dismiss your point overall, but I see that example so often and it irks me so much.
Unit tests are your specification. So, 1) ideally you should write the specification before you implement the functionality. But also, 2) this is the one part where you really should be putting in your critical thinking to work out what the code needs to be doing.
An AI chatbot or autocomplete can aid you in putting down some of the boilerplate to have the specification automatically checked against the implementation. Or you could try to formulate the specification in plaintext and have an AI translate it into code. But an AI without knowledge of the context nor critical thinking cannot write the specification for you.
Also after your 4th proper project you won’t be as confused about “how to get started” anymore anyway.
You have a language of choice, a gui framework, and a build system you are comfortable with in mind already just start making folders.
Feels like there are some fine people here only working on new projects. Getting started could be, breaking down a 20 year old program, written in some wierd manner because the original developer use to do functional programming but was told to use java and oop. No comments, no tests, no normal patterns, no documentation.
The argument was “AI helps when starting up new projects by making unit tests etc.”
Also for not 20, but even building 10 year old libraries using AI is unhelpful. It just keeps hallucinating non-existent packages and functions.
At this point just drive yourself crazy while promising to become goose farmer and commenting every single line in your own words like god intended for programmers to do.
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?
Can someone tell me what vibe coding is?
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.
And to add to this, you don’t actually do any coding yourself. Just using something to help with boilerplate code isn’t usually counted.
Although, I’m wondering from this Reddit r/vibecoding thread if that’s a Lemmy-specific definition. Most of the people in it seem to be using LLMs in a sane way and are telling OP this isn’t.
My entire IT career has been funded by morons like this. This is just the latest moronic idea that is going to pay my bills. Cleaning up after vibe coders has guaranteed my income until I die. You see, posts like this focus on the code that is broken and requires another dev to fix it enough to get it going. There is a long road from “finally working” to “production ready” to “optimized”, and we get paid along every inch of the way.
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.
deleted by creator
I don’t really care about vibe coders but as a dev with just under 2 decades in the field:
- Your vibe coding shit will not go to prod until humans fully review it
- You better review it yourself first before offloading that massive mental drain to someone else (which means you still need to have some semblance of programming skills). Don’t open a PR with 250 files in it and then tell someone else to validate it.
- Use more context. Don’t give it vague ass prompts.
- Don’t use auto-accept. That’s just lazy asshole shit.
I can’t stress this enough: if you give me a PR with tons of new files and expect me to review it when you didn’t even review it yourself, I will 100% reject it and make you do it. If it’s all dumped into a single commit, I will whip your computer into the nearest body of water and tell you to go fish it out.
I don’t care what AI tool wrote your code. You’re still responsible for it and I will blame you.
When I see a sloppy PR I remind people “AI didn’t write that. You wrote it. Your name is on the git blame.”
Love it, I have a vibe coding colleague I will use this with.
I like this mentality. I might start telling people the same thing
I have never used an AI to code and don’t care about being able to do it to the point that I have disabled the buttons that Microsoft crammed into VS Code.
That said, I do think a better use of AI might be to prepare PRs in logical and reasonable sizes for submission that have coherent contextualization and scope. That way when some dingbat vibe codes their way into a circle jerk that simultaneously crashes from dual memory access and doxxes the entire user base, finding issues is easier to spread out and easier to educate them on why vibe coding is boneheaded.
I developed for the VFX industry and I see the whole vibe coding thing as akin to storyboards or previs. Those are fast and (often) sloppy representations of the final production which can be used to quickly communicate a concept without massive investment. I see the similarities in this, a vibe code job is sloppy, sometimes incomprehensible, but the finished product could give someone who knew what the fuck they are doing a springboard to write it correctly. So do what the film industry does: keep your previs guys in the basement, feed them occasionally, and tell them to go home when the real work starts. (No shade to previs/SB artists, it is a real craft and vital for the film industry as a whole. I am being flippant about you for commedic effect. Love you guys.)
I think this is great. I like hearing about your experience in the VFX industry since it’s unfamiliar to me as a web dev. The storyboard comparison is spot on. I like that people can drum up a “what if” at such a fast pace, but vibe coders need to be aware that it’s not a final product. You can spin it up, gauge what works and what doesn’t, and now you have feasibility with low overhead. There’s real value to that.
Edit: forgot to touch on your PR comment.
At work, we have an optional GitHub workflow that lets you call Claude in a PR and it will do its own assessment based on the instructions file we wrote for it. We stress that it’s not a final say and will make mistakes, but it’s been good in a pinch. I think if it misses 5 things but uncovers 1 bug, that’s still a win. I’ve definitely had “a-ha” moments with it where my dumb brain failed to properly handle a condition or something. Our company is good about using it responsibly and supplying as much context as we possibly can.
I like your previs analogy, because that’s how I’ve been thinking of it in my head without really knowing how to communicate it. It’s not very good at making a finished project, but it can be useful to demonstrate a direction to go in.
And actually, the one time I’ve felt I was able to use AI successfully was literally using it for previs; I had a specific idea of design I wanted for a logo, but didn’t know how to communicate it. So I created about a hundred AI iterations that eventually got close to what I wanted, handed that to my wife who is an actual artist, told her that was roughly what I was thinking about, and then she took the direction it was going in and made it an actual proper finished design. It saved us probably 15-20 iterations of going back and forth, and kept her from getting progressively more annoyed with me for saying “well… can you make it like that, but more so?”
If it’s all dumped into a single commit, I will whip your computer into the nearest body of water and tell you to go fish it out.
I’m going to steal this for an update to an internal guidance document for my dev team. Thank you.
Lmao glad I could help! I hate those big commits. They’re so much harder to traverse and know what’s going on. Developer experience has been big on my mind lately. Working 5 days a week is already hard, but there are moments when we can make tiny bits easier for each other.
imo paying devs to review vibe coded bile would not work either. At best, the dev themselves should do the vibe coding.
Someone who has no clue whatsoever in terms of programming cannot give it the right prompt.
Yeah, this is my nightmare scenario. Code reviews are always the worst part of a programming gig, and they must get exponentially worse when the junior devs can crank out 100s of lines of code per commit with an LLM.
Swear to god the vibe coding movement is going to create so many new jobs in the ilk of “I hired some dude to write my startup thing and now it’s gone all to shit, can you make it actually good and scalable and responsive please?”
"What do you do? “Oh, I work in AI Disaster Response”
Obviously fake. Still funny though.
You should(n’t) watch Quin69. He’s currently “vibe-coding” a game with Claude. Already spent $3000 in tokens, and the game was in such a shit state, that a viewer had to intervene and push an update that dragged it to a “playable” state.
The game is at a level of a “my first godot game”, that someone who’s learning could’ve made over a weekend.
I better not watch this, it would make me angry. I hate people who could have hired someone like me for the same or even less money and get a working product. But no, they always throw money at fraudsters. Because wasting resources is their very nature.
Are you saying the comment is fake, or the sentiment? This was actually posted to reddit: https://archive.is/U9ntj
Fake in that it’s almost assuredly written and posted by someone who is actively anti-vibe coding and this is a troll on the true believers.
Correct.
I love the one guy on that thread who is defending vibe coding, and is “about to launch his first application,” and anyone who tells him how dumb he is is only doing so because they feel threatened.
Nah I’m on that guy’s side. His experience lines up with my own, namely that vibe coding is not useful for people who don’t know how to program, but it can be useful for people who do know how to program, and simply aren’t familiar with the specific syntax used in a language they’re not an expert in.
In that case, the queries to the AI model aren’t, “write me a program that can do X”, it’s more like “write me a function in this language that can take A, B, and C as inputs, do operation Y with them, and return Z”, or “what’s the best way to find all of the unique elements in an array and sort it alphabetically in this language”. Then the programmer can take those pieces and build up a proper application with them. The AI isn’t actually writing the program for you, it’s more like a customized Stack Overflow generator, without having to wade through a decade of people arguing back and forth in the comments about inane bullshit.
Does it save a ton of time? No, but it’s still helpful, and can get you up and running in a new language much faster than the alternative.
Sure, it can be useful for people who do know how to program, though I find it usually takes more effort to get it to create what I want and make sure it works than it takes to just do it myself.
This guy explicitly says he doesn’t know how to program though. He says he took an HTML (not a programming language, a markdown language) class a decade ago. He probably doesn’t remember shit from it, not that it’d be helpful anyway because writing HTML has nothing to do with writing a program to perform a task.
Does it save a ton of time? No, but it’s still helpful, and can get you up and running in a new language much faster than the alternative.
You obviously aren’t a programmer. You either know how to program or you don’t. The language is just syntax, which is trivial to learn. It doesn’t help you get running in a new language because you still need to learn the syntax to make sure it’s writing something reasonable. That time has to be spent no matter what.
I’m currently doing this with an angular project that’s a bit of a clusterfuck. So many layers.
I’m still having to break it down into much, much smaller chunks and it’s not able to do much, but it is helpful. Most useful thing was that I started with writing a pure SQL query with several joins and told it “turn this into linq using existing entities”.
I think they’ll completely replace ORMs.
An HtML class ten years ago isn’t anything close to knowing how to program. It’s like saying “I wrote a bullet point lost years ago so I know how to write a novel.”
It’s strange, but I’ve seen lots of comments that are not aware this is fake. The ai hater crowd is using it as their proof, the other side saying he is using it wrong.
That’s depressing. This is so obviously fake because of how entertaining it is written and how the conclusion gets shoved in your face. No subtlety.
Is that what the weird extra width on some letters is, artifacts from some AI generating the post?
No, the phrasing makes it clear someone wrote a fictional account of becoming self aware that the output of vibe coding isn’t maintainable as it scales.
I’m entirely too trusting and would like to know what about the phrasing tips you off that it’s fictional. Back on Reddit I remember so many claims about posts being fake and I was never able to tease out what distinguished the “omg fake! r/thathappened” posts from the ones that weren’t accused of that, and I feel this is a skill I should be able to have on some level. Although taking an amusing post that wasn’t real as real doesn’t always have bad consequences.
But I mostly asked because I’m curious about the weird extra width on letters.
When something is too “on the nose,” for example, it’s written in exactly the way that would induce the most cheering and virality because it appeals so much to one group of people, it’s worth considering it may have been written to provoke exactly that reaction.
Thanks!
I really wish people did not do this. This isn’t something I was ever taught to look for, and I like to think I got a good education. I was taught to make sure my source is credible, to consider biases and spin and what things are facts and what is just opinion, but I wasn’t taught to look for a lot of deception people call out online. But I guess I have to live with this and gain the skill to look for deception. Genuinely, thanks for helping me, since I don’t think I ever would have figured out what raises “fake” flags in most peoples’ heads on my own.
AmidFuror’s description is on point and I see it as a variant of Poe’s Law. Instead of sarcasm being mistaken for a real belief, it is presenting a fictional account of someone being self aware that is mistaken for someone actually becoming self aware.
There are two lines that make me absolutely certain it is written by someone who it not a vibe coder and is leaning into the sarcasm.
- ‘pulling out my wallet for someone that knows what they are doing’ implies the poster knows they don’t know what they are doing
- ‘vibe coding is just roleplaying for guys who want to feel like hackers’ is a joke I’ve seen directed at vibe coders more than once
Keep in mind that not all deception is malicious, but most people see the word deception as having a negative implication. An actor/actress pretending to be someone else is technically deceptive the same way as whoever wrote this hilarious post. They are presenting a fictional account for an audience.
You are right about the thespian thing, but when you watch TV/film/theatre everyone is in on the “joke” and we all know they’re not really falling in love, getting murdered, or whatever dramatic happening. I’m not sure if OOP is just trying to entertain and expects everyone to realize they’re joking, which would stick them on the thespian side, or if they have other motives. But hey, interesting point to bring up!
You are right about the thespian thing, but when you watch TV/film/theatre everyone is in on the “joke” and we all know they’re not really falling in love, getting murdered, or whatever dramatic happening. I’m not sure if OOP is just trying to entertain and expects everyone to realize they’re joking, which would stick them on the thespian side, or if they have other motives. But hey, interesting point to bring up!
r/thatHappened was the worst thing to happen to Reddit and I sincerely hate whoever created that sub
No, the text itself. No vibe coder would write something like that. The artifacts you mentioned are the result of simple horizontal and vertical upscaling. If you zoom in you can see it better.
Thanks!
You’e welcome!
Best erotic story ever on !DevsGoneWild@lemmynsfw.com <3
I wish that was a real sub
Somebody make this a sub pls
Why does this image look like an AI-generated screenshot? The letter spacing and weights are all wrong.
It’s a real post on Reddit. I don’t know what combination of screenshotting/uploading tools leads to this kind of mangling, but I’ve seen it in screenshots from Android, too. The artifacts seem to run down in straight vertical lines, so maybe slight scaling with a nearest-neighbor algorithm (in 2025?!?) plus a couple levels of JPEG compression? It looks really weird.
I’m curious. If anyone knows, please enlighten me!
Oh, if it’s just a random Android fork/version being terrible at something, I understand now. Maybe it’s a phone with a screen that isn’t standard in someway.
probably
