[commandersaki]

I really respect Mitchell's response to the OpenAI accident, even if it is seen in positive light for ghostty. Can't think of any software vendor that actively tries to eliminate nag / annoyances (thinking specifically of MS Auto Update), so this is welcome.

Also this article shows responsible use of AI when programming; I don't think it fits the original definition of vibe coding that caused hysterics.

[dlvhdr]

yeah the usage of "vibe coding" here doesn't fit at all. That term is so overused.

[simonw]

Worth noting that Mitchell didn't actually use the term "vibe coding" anywhere in this article.

He called it "vibing" in the headline, which matches my suspicion that the term "vibe" is evolving to mean anything that uses generative AI, see also Microsoft "vibe working": https://www.microsoft.com/en-us/microsoft-365/blog/2025/09/2...

[mitchellh]

I'll add the title is a bit of bait. I don't use the word "vibe" (in any of its forms) anywhere outside of the title.

I'm not baiting for general engagement, I don't really care about that. I'm baiting for people who are extremist on either side of the "vibe" spectrum such that it'd trigger them to read this, because either way I think it could be good for them.

If you're an extreme pro-vibe person, I wanted to give an example of what I feel is a positive usage of AI. There's a lot of extreme vibe hype boys who are... sloppy.

And if you're an extreme anti-vibe person, I wanted to give an example that clearly refutes many criticisms. (Not all, of course, e.g. there's no discussion here one way or another about say... resource usage).

So, sorry!

[wahnfrieden]

It has simply evolved from its initial meaning, as language does.

[afro88]

> Also this article shows responsible use of AI when programming; I don't think it fits the original definition of vibe coding that caused hysterics.

Yep. It's vibe engineering, which simonw coined here: https://simonwillison.net/2025/Oct/7/vibe-engineering/