Any opinions on "vibe coding"?
-
You can save time at the cost of headaches, or you can save headaches at the cost of time. You cannot save both time and headaches, you can at most defer the time and the headaches until the next time you have to touch the code, but the time doubles and the headaches triple.
-
I've seen this term thrown around a lot lately and I just wanted to read your opinion on the matter. I feel like I'm going insane.
Vibe coding is essentially asking AI to do the whole coding process, and then checking the code for errors and bugs (optional).
Somewhat impressive, but still not quite a threat to my professional career, as it cannot produce reliable software for business use.
It does seem to open up for novices to create 'bespoke software' where they previously would not have been able to, or otherwise unable to justify the time commitment, which is fun. This means more software gets created which otherwise would not have existed, and I like that.
-
I've seen this term thrown around a lot lately and I just wanted to read your opinion on the matter. I feel like I'm going insane.
Vibe coding is essentially asking AI to do the whole coding process, and then checking the code for errors and bugs (optional).
lol wut, asking AI to do the work and then going back and fixing bugs…?
To me, vibe coding is pick a project to work on and get building. Very basic planning stages without much design, like building with legos without instruction manuals. I make design decisions and refactor as I code. I certainly get some AI input when I don’t know how to implement something, but I will usually work “blindly” using my own ideas and documentation. I probably visit stackoverflow while vibe coding more than I do chatgpt.
-
I've seen this term thrown around a lot lately and I just wanted to read your opinion on the matter. I feel like I'm going insane.
Vibe coding is essentially asking AI to do the whole coding process, and then checking the code for errors and bugs (optional).
I mean, at some point you have to realize that instructing an AI on every single thing you want to do starts to look a lot like programming.
Programming isn't just writing code. It's being able to reason about a method of doing things. Until AI is at the level of designer, you can expect humans to have to do the brunt of the work to bring software to life.
-
I mean, at some point you have to realize that instructing an AI on every single thing you want to do starts to look a lot like programming.
Programming isn't just writing code. It's being able to reason about a method of doing things. Until AI is at the level of designer, you can expect humans to have to do the brunt of the work to bring software to life.
Yeah, there’s also the “debugging is just as hard as writing elegant code” side of things. Vibe coding is largely just putting yourself in a permanent debugging role.
The big issue I see with vibe coding is that you need to know best practices to build secure code. Even if you don’t adhere to them all the time, best practices exist for a reason. And a programmer who doesn’t even know them is a dangerous thing, because they won’t even be able to see what is insecure (until it’s far too late).
Studies have found that vibe coders tend to produce less secure code, but have higher confidence in their code being secure; It’s essentially Dunning-Kruger in practice. I’d have no issue with someone using AI to get the broad strokes down. But then they need to be able to back it up with actual debugging. Not just “I didn’t even bother looking at it. If it compiles, push it to prod.”
-
I've seen this term thrown around a lot lately and I just wanted to read your opinion on the matter. I feel like I'm going insane.
Vibe coding is essentially asking AI to do the whole coding process, and then checking the code for errors and bugs (optional).
I like writing code. Like, physically typing it. It's fun and probably my favorite pastime.
Why would I wanna give that up?
-
I like writing code. Like, physically typing it. It's fun and probably my favorite pastime.
Why would I wanna give that up?
-
Seems like a recipe for subtle bugs and unmaintainable systems. Also those Eloi from the time machine, where they don't know how anything works anymore.
Management is probably salivating at the idea of firing all those expensive engineers that tell them stuff like "you can't draw three red lines all perpendicular in yellow ink"
I'm also reminded of that ai-for-music guy that was like "No one likes making art!". Soulless husk.
Three perpendicular lines are possible in 3D, and saffron is initially red, but becomes yellow when used in cooking. Checkmate!
-
I've seen this term thrown around a lot lately and I just wanted to read your opinion on the matter. I feel like I'm going insane.
Vibe coding is essentially asking AI to do the whole coding process, and then checking the code for errors and bugs (optional).
I think calling that vibe coding is a very unfitting term. I haven't seen it called that before.
-
Nearly every time I ask ChatGPT a question about a well established tech stack, it's responses are erroneous to the point of being useless. It frequently provides examples using fabricated, non-existent functionality and the code samples are awful.
What's the point in getting AI to write code that I'm just going to have to completely rewrite?
Gell-Mann Amnesia effect
-
System shared this topic
