[chucknthem]

Funny I'm a professional engineer and happily call myself "vibe coding" when writing code these days, it started as tongue in cheek, but now I've embraced it.

Being good at vibe coding is just being good at coding, the best practices still apply. I don't feel we need another term for it. It'll just be how almost everyone writes code in the future. Just like using an IDE.

[DowsingSpoon]

If you’re looking at the AI-generated output then you’re not Vibe Coding. Period. Let’s not dilute and destroy the term just as it’s beginning to become a useful label.

[gonzo41]

Wait, are people not reading the AI code they use?

[jrk]

People of course often do read (and even modify) the model-generated code, but doing so is specifically not “vibe coding” according to the original definition, which was not meant to encompass “any programming with an LLM” but something much more specific: https://simonwillison.net/2025/Mar/19/vibe-coding/

[rglynn]

The whole point of the term is to convey that you are only looking at the output and not looking under the hood. If vibe coding a UI, you only look at the UI, not the CSS.

[caseyohara]

Nope. That's the "vibe" part of Vibe Coding™.

> The developer does not review or edit the code, but solely uses tools and execution results to evaluate it and asks the LLM for improvements. Unlike traditional AI-assisted coding or pair programming, the human developer avoids examination of the code, accepts AI-suggested completions without human review, and focuses more on iterative experimentation than code correctness or structure.

https://en.wikipedia.org/wiki/Vibe_coding

[AdieuToLogic]

> Being good at vibe coding is just being good at coding, the best practices still apply.

How does "vibe coding" embody "best practices" as the industry generally defines the latter term?

As I understand the phrase "vibe coding", it implies focusing solely on LLM prompt formulation and not the specifics of the generated source.

> It'll just be how almost everyone writes code in the future. Just like using an IDE.

The flaw with this analogy is that a qualified developer does not require an IDE in order to be able to do their job.

[witx]

> vibe coding is just being good at coding

Having someone cook my dinner's ingredients is just (me) being a good cook ...

[keithnz]

likewise, for a lot of frontend I "vibe code" it. I mostly don't look at the code anymore while doing it either, after I get where I want, I will look through the code and maybe clean stuff up. But a lot of the code is fine. Works really well I find. (using Augment Code with Claude Sonnet 4.5).