[0xblacklight]

tbh I think the thing that's making this new approach so hard to adopt for many people is the word "vibecoding"

Like yes vibecoding in the lovable-esque "give me an app that does XYZ" manner is obviously ridiculous and wrong, and will result in slop. Building any serious app based on "vibes" is stupid.

But if you're doing this right, you are not "coding" in any traditional sense of the word, and you are *definitely* not relying on vibes

Maybe we need a new word

[simonw]

I'm sticking to the original definition of "vibe coding", which is AI-generated code that you don't review.

If you're properly reviewing the code, you're programming.

The challenge is finding a good term for code that's responsibly written with AI assistance. I've been calling it "AI-assisted programming" but that's WAY too long.

[greymalik]

It’s just programming. We don’t use a different word for writing code in an IDE either.

[dhorthy]

we can come up with something better :)

[dhorthy]

alex reibman proposed hyperengineering

i've also heard "aura coding", "spec-driven development" and a bunch of others I don't love.

but we def need a new word cause vibe coding aint it

[Xss3]

Vibe coding is accepting ai output based on vibes. Simple as that.

You can vibe code using specs or just by having a conversation.

[chickensong]

AI is the new pAIr programming.