Programming

18918 readers

332 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Any opinions on "vibe coding"? (lemy.lol)

submitted 1 day ago by KazuchijouNo@lemy.lol to c/programming@programming.dev

34 comments fedilink hide all child comments

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).

you are viewing a single comment's thread
view the rest of the comments

[–] cool@lemmings.world 2 points 5 hours ago (1 children)

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.

[–] PM_Your_Nudes_Please@lemmy.world 1 points 1 hour ago

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.”