To me "vibe coding" is like Karpathy wrote in that tweet: You completely surrender to the model, accept everything, never look at the changes in code. Only feed prompts and check the resulting product.

But, of course, that's not how most programmers use - at least I'd like to think. One thing is when people with zero programming knowledge vibe code something in that fashion, but for serious (read: big) products I'd like to think that you're still forced to do some book keeping.

I've done some personal CRUD stuff like that. Worked well - I fixed bugs as I found them, only hit one thing it couldn't do (I find codex weak at front-end stuff generally).

Would never publish it though, or approach paid work like that.