Programming

18918 readers

327 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

35 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

[–] NeuroByte@lemm.ee 2 points 11 hours ago

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.