The vibecoders are becoming sentient
-
what vibe coding? do i really want to know?
Letting Clippy Jr write your code.
-
This post did not contain any content.
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.
-
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.
-
This post did not contain any content.
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?
-
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.)
wrote last edited by [email protected]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.
-
This post did not contain any content.
Can someone tell me what vibe coding is?
-
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.
wrote last edited by [email protected]I'd probably just use that 3D model to do a retopo.
-
Can someone tell me what vibe coding is?
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.
-
Can someone tell me what vibe coding is?
Simply not caring and letting the dice roll machine drive
-
This post did not contain any content.wrote last edited by [email protected]
AI used extremely sparingly is sometimes helpful to an experienced coder. "Multivac, 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.
-
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 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?”
-
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.
-
AI used extremely sparingly is sometimes helpful to an experienced coder. "Multivac, 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.
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.
-
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.
wrote last edited by [email protected]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.
-
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.
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.
-
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.
wrote last edited by [email protected]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.
-
This post did not contain any content.
Consulting opportunity: clean up your vibe-coding projects and get them to production.
-
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.
-
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. -
AI used extremely sparingly is sometimes helpful to an experienced coder. "Multivac, 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.
