Hacker News Reader

I'm starting to think of "vibe coding" as "peer/pair programming". How effective it will be depends on how effective I am as the peer reviewer.

The driver is the AI who is highly capable but has a 5% chance of doing something psychotic lol. Me, the peer, can either review carefully and catch errors or just relax and "vibe" through it all. Results will of course vary based on that relationship.

View on HN

"Vibe coding" was intended to mean where you don't pay attention to the work your partner creates at all. Where you just lean into their "vibe" and run with it, no matter how bad it actually is. What you describe already has a name. You even mentioned it yourself. Also calling it "vibe coding" would be a bit redundant.

No Vibe Coding is when you dont touch the code yourself and only ask the LLM to make edits for you. You still understand and make sure llm does what you asked, but you dont touch the code yourself.

That wasn't the original intent. It was described as "fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists".

It may have come to mean what you describe to some, but that's more commonly what we call managing a junior engineer. As before, no need for redundancy.

Reply on news.ycombinator.com