This X post from Julia Turc is old but prompted me to write.

The term "vibe code" is silly. It's simply AI-assisted coding. Full stop.

You're coding. It doesn't matter whether you're coding solo, with AI or multiple models, with off-shore freelancers, or with a gaggle of geese.

You're coding.

Now, the impetus to code? That's way more important to communicate.

If you wish to define "vibe coding" as building for yourself, for experimenting, for prototyping, for shipping something from a v0.1 to a v1.0—sure, knock yourself out.

I know others like the "vibe" because of the synergy they achieve building something with AI. If that's your definition, you're welcome to it.

But humans have already come up with words and phrases that better explain the work than vibe code. I use:

• Prototyping Code: When the code doesn't ship

• Production Code: When the code does ship

Simpler? Yes. Less ambiguous? Also yes. Less trendy? Definitely. Boomer? Possibly.

But I've always preferred to describe my work plainly, rather than "vibe think" fancy new phrases for how I work.