I don’t think the two cross, really. A vibe coder asks for a bunch of features and then starts refining the output, fixing bugs and adding features. A developer knows the specific architecture and from years of writing tasks knows how to break work into manageable chunks and uses AI to implement something they have already defined and know where it fits in. The skill to write a good story isn’t far off from sitting a good prompt.
I use AI all the time, and every time I hear someone describing vibe coding it makes my skin crawl.
Buffalobuffalo@reddthat.com 6 hours ago
The definition may have changed but I feel like originally it was only vibe coding when the “dev” did not know what they are doing. When some one with little to no programming background is able to build and app on “vibes” alone.
Serinus@lemmy.world 3 hours ago
Also applies when the dev could know what they’re doing, but just doesn’t care to.
dis_honestfamiliar@lemmy.sdf.org 4 hours ago
Well then, I’ve been doing this all wrong.
webghost0101@sopuli.xyz 5 hours ago
My first interpretation of vibe coding was to code for fun and personal enjoyment without worrying about industry standards or deployability. More often see with self-taught youth.
I felt like i have been doing this for years before ai became a thing.