this post was submitted on 15 Sep 2025
135 points (82.6% liked)
Technology
75162 readers
1580 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm well aware the plural of "anecdote" isn't "data", but literally no dev I know (senior or otherwise) thinks this. Give me a junior work with - most of them at least actually learn.
Yeah it’s the same skillset I use with Junior devs except I don’t have the hope AI will grow out of its bad habits
Amen. I've tried the vibe coding thing but it's frustrating because a) too often the AI output has some profound problems and it gets annoying 'babysitting' it; and b) I usually prefer the challenge of figuring out syntax and implementation issues myself.
If something is taking too long I'll ask the LLM. But I feel like if I do this too much my skill set will atrophy and I'll lose my sharpness. So it's a balancing act.
But this brings up another wider question: where is the line between "occasionally getting AI help" and "vibe coding"? Surely it's subjective.
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.
Also applies when the dev could know what they're doing, but just doesn't care to.
Well then, I've been doing this all wrong.
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.
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 writing a good prompt.
I use AI all the time, and every time I hear someone describing vibe coding it makes my skin crawl.
I'd say the use cases of: mundane but time consuming, pointed inquiries or interactive rubber ducking, are all getting AI help. Offloading a design where you don't have a clear understanding of how it should be done is vibing.