[dwb]

Both you and the Collins dictionary (merely one dictionary, not an absolute anuthority) are retconning. “Vibe coding”, as originally coined in this tweet, means something more specific: to generate code with LLMs and not really look at the output. The term itself suggests this too: reviewing code is not exactly a vibes-based activity, is it?

https://xcancel.com/karpathy/status/1886192184808149383

[tovej]

Here's Merriam Webster with the same definition: https://www.merriam-webster.com/dictionary/vibe%20coding

That tweet coins the term, we agree there. The activity it describes is using natural language to generate software. Whether you add a review process or not doesn't substantially change that. Sure, Karpathy says he doesn't "read the diffs anymore". Why does he say "anymore"? Clearly he was reading them at some point. If not reading any diffs was a core part of the activity, that wouldn't be the case, the tweet itself clearly outlines that as optional. He's clearly not talking about a core part of the activity.

[dwb]

I think the tweet is pretty clear on its intention for the definition and I’m not interested in arguing about it.

I do think the dictionary definitions, such as they are, are coming from a real place: some people do use the more general definition. And you seem to already know about both definitions. So why argue so belligerently and definitively in the first place? Parent comments you were replying to were obviously using the original definition. Talking about “retconning” is obviously silly given this timeline. Meaning in language is not a race to be the first to make it into a dictionary. It’s a very new phenomenon that new terms make it so quickly into a dictionary at all, and they’re always under review. So maybe factor that into your commentary?

[tovej]

Because I believe the broad definition is more widely used, I also don't think the narrow term is useful or meaningful, and I think it's being used purely by vibe coding practitioners who feel that the term has negative connotations.

This all started with the parent comment telling someone else (belligerently and definitively) using the broader definition that they were wrong.

[dwb]

The narrow term is very useful, there is obviously a world of difference between reviewing the output of an LLM and not - the latter is irresponsible. It shouldn’t be surprising that people bristle when being accused of it. It doesn’t make sense to accuse someone of redefining a term to make themselves feel better when the history of the term shows that yours is the redefinition. The simpler explanation is that the accused just doesn’t like being called irresponsible - not that they’re trying to defend LLM code generation from someone who doesn’t like it.

[tovej]

You're saying what I'm saying. They feel self conscious about the term "vibe coding".

And to be clear, nobody accused the people who lashed out here. They reacted to general statements that people are vibe coding.

I also don't understand why the term vibe coding couldn't contain a spectrum of responsible use. Just say you're reviewing your vibe coded commits!

Clearly the issue here is about how vibe coders perceive the term vibe coding. Some of them feel that it's demeaning and are trying to wiggle their way out of the label by arguing semantics.

[dwb]

No, people think it’s demeaning because they are using a different definition to you, the definition which was the original one. Don’t know how I can put it clearer.