> because that's the definition of vibe coding.

That's _your_ definition of vibe coding.

> Karpathy described it as a form of coding where you "fully give in to the vibes, embrace exponentials, and forget that the code even exists"

If that's not "turning your brain off", what is?

That's the definition I am aware of, yes. It's also in the term, that you let a vibe (a force coming from the outside) decide what your work lead to, as opposed as to deciding where it should arrive at and leading into that direction.

What is your definition? Is there any difference between AI assisted development and vibe coding to you?

Feels like a No True Scotsman fallacy.

There's multiple ways to program using LLMs, so using different words for different styles is a useful distinction.

Of course, you absolutely can build a No True Scotsman argument on top of that distinction, but I don't think that's what GP was doing.

How so?

The property Scotsman is existing a priori and then a causality to behaviour is assumed. But here the term is defined by behaviour.

By that logic every appeal to the truth is a No True Scotsman fallacy.

I agree. It’s actually more exhausting in some ways.