upvote

points

by malisper10 hours ago |
comments
upvoteby nailer10 hours ago|
[-]
> I suspect it's less of an undertaking than you may think... having an existing codebase you can reference prevents a lot of the problems you have with vibecoding.

That's because it's not vibe coding - stingraycharles doesn't seem to understand what vibe coding is. Vibe coding was defined here https://x.com/karpathy/status/1886192184808149383

> There's a new kind of coding I call “vibe coding”, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.

This is very far from Anthropic's migration plans.

reply
upvoteby andai10 hours ago|
parent|
next
[-]
Yeah, it's a distinction worth making, and the language for making it kind of sucks. Vibe coding means "AI does the whole thing", or "I use tab autocomplete" depending on who you ask. It's not a very useful term anymore, we need better ones.

My benchmark is basically, "are you letting the AI drive."

In this case, an AI appears to have written the migration guide...

reply
upvoteby wrs10 hours ago|
parent|
next
[-]
It was and is a perfectly good term, but people started using it without regard for its definition. I don't know why people wouldn't misuse a "better" term the same way.
reply
upvoteby kelnos9 hours ago|
parent|
[-]
In this case I think the current zeitgeist (at least among zoomers and younger millennials) really loves the word "vibe". Once they hear of the term "vibe coding", they just want to be able to say it, even if what they're doing isn't really vibe coding.

And then that leaks outside their social and age groups, because other people hear the incorrect usage, get confused, and incorporate that confusion into their own use of the term.

reply
upvoteby uncircle7 hours ago|
parent|
[-]
Waiting until they decide to call non-assisted programming ‘unc coding’
reply
upvoteby kelnos7 hours ago|
parent|
[-]
As someone who might be described as an "unc", I had to look up what "unc" meant.
reply
upvoteby c0rruptbytes10 hours ago|
parent|
prev|
[-]
i mean AI docs are usually the result of collabs between users and AI using /plan

with superpowers, i see a lot of specs -> impl plan -> execute plan

reply
upvoteby andai4 hours ago|
parent|
[-]
Yeah. It "might be" that a human actually looked at it. There's just no way to know anymore. So it rightly doesn't inspire confidence.
reply
upvoteby brabel6 hours ago|
parent|
prev|
next
[-]
You are right but recently, vibe coding has become a demeaning term for AI assisted code by anti-AI people. It’s interesting seeing how words evolve very quickly on the internet as they spread to different demographics.
reply
upvoteby Jtarii5 hours ago|
parent|
prev|
next
[-]
That is one person's definition of vibe coding, not "the definition" of vibe coding. Words have multiple meanings.
reply
upvoteby andai4 hours ago|
parent|
next
[-]
Just going off vibes and not even looking at the code was the original definition. But "different people say the same thing but mean different things" is kind of the problem I was getting at.
reply
upvoteby nailer29 minutes ago|
parent|
prev|
[-]
It’s the person that created the term’s definition.
reply
upvoteby bitwize10 hours ago|
parent|
prev|
next
[-]
"Vibe coding" = "let Dario take the wheel" as ThePrimeagen puts it.
reply
upvoteby 10 hours ago|
parent|
prev|
[-]
deleted
reply