The vibecoders are becoming sentient
-
This post did not contain any content.
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?"
-
This post did not contain any content.
How does one distort an image like this on accident?
-
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.
-
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!
They knew the two lines that I quoted would clue in most people who dislike vibe coding that it was a joke.
-
what vibe coding? do i really want to know?
Getting LLMs to write all your code
-
what vibe coding? do i really want to know?
it's buzzword speak for "connect chatgpt to your editor, tell it what you want, and blindly accept the answer"
-
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.
-
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.”
-
Getting LLMs to write all your code
geez in my day i had carefully curated snippets in my text editor and i loved it.
-
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.
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.
-
This post did not contain any content.wrote last edited by [email protected]
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.
-
Are you saying the comment is fake, or the sentiment? This was actually posted to reddit: https://archive.is/U9ntj
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.
-
This post did not contain any content.
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.
-
When I see a sloppy PR I remind people “AI didn’t write that. You wrote it. Your name is on the git blame.”
I like this mentality. I might start telling people the same thing
-
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" -
It's like the nerd version of Synthol body 'builders'.
Well
That's horrifying. I thought it was way cooler that I could make my own muscles bigger by diet and exercise but maybe cool is different in different parts of the world
-
Well
That's horrifying. I thought it was way cooler that I could make my own muscles bigger by diet and exercise but maybe cool is different in different parts of the world
wrote last edited by [email protected]That's horrifying.
I have no empirical evidence... but I'm fully convinced there's at least 1 idiot with a synthol pp
-
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.
wrote last edited by [email protected]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.
-
Obviously fake. Still funny though.
wrote last edited by [email protected]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 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.
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.)
