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

▲

wrs 4 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.

▲

kelnos 2 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.

▲

uncircle an hour ago | parent [-]

Waiting until they decide to call non-assisted programming ‘unc coding’

	▲	kelnos an hour ago \| parent [-]
		As someone who might be described as an "unc", I had to look up what "unc" meant.

▲

c0rruptbytes 4 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