[azthecx]

No, with vibe coding you are not a reviewer an editor or an author, quoting from the source:

    There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
    ...
    I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.

[jey]

Odd. How can one get the vibes without looking at the code? Like gleaming diamond vibes versus confused spaghetti vibes.

[NoahKAndrews]

I think the vibes refer to the running software, not to the code itself. I hate the whole concept deeply.

[ZeroTalent]

No, they actually have the files pane on the left, live preview mid-top, terminal errors mid-bottom, and the agent on the right. no looking at code.

Cursor has a "yolo mode" where you don't have to click accept for tooling even for system commands and people whitelist commands like sudo, su, and rf :))) I wish I was kidding.

[danielbln]

The vibes are coming from changing to actual product (design, UX, functionality) and not from the code. The code in fact doesn't matter at all. At this point that's only ok for throwaway prototypes (but for those it's quite wonderful), the more the application requires careful maintainable engineering, you need to read every line and leash the LLM. It's a bit of a continuum between the two edges in reality.

[CharlesW]

> No, with vibe coding you are not a reviewer an editor or an author, quoting from the source:

That was the joke, which Karpathy found "quite amusing" and "not too bad for throwaway weekend projects". In reality, you won't even get that far with vibe coding if you don't understand what's going on.