[benatkin]

A vibe is intuition, so it can't be too much, else it isn't vibe coding. However, the intuition that comes after taking some time is different than after a quick glance. For instance if you read a pull request and then immediately decide after reading it at a measured space that would be different than after skimming it. So yes, Looks OK to me right now, or LGTM, as in a pull request, is what I have in mind.

[gregjor]

Intuition comes from deep understanding, a set of learned heuristics. That implies experience that lets you skim and trust your quick judgment. And it informs the probability you assign to the correctness of your judgment.

As I understand it vibe coding and “vibe check” refer merely to “a looks good to me” feeling with no deep understanding, not knowing what you don’t know, which ignores security holes and edge cases.

If my kids “vibe code” a fort with cardboard boxes and blankets they have a different intuition about stability, security, longevity, and the purpose of a fort than I do.

[benatkin]

I guess a full time vibe coder would develop an intuition based on experiences with vibe coding and launching stuff and getting feedback. This process would increase their level of understanding and intuition.

[gregjor]

We will all form an intuition about "vibe coding" before too long, probably not a positive intuition. I'd suggest people "launching stuff" in hopes of feedback would label their work as "vibe coding" to warn prospective users, but for now at least that will be obvious, like a child's cardboard fort obviously can't pass for a real fort.

Someone could "vibe bake" cakes by trial and error with the help of AI, then try to sell them and get feedback. That might work, or they might poison someone. Alternately they could learn how to bake and study baking to develop actual skills and understand what they're doing.