Comment by stavros
As someone who can program and used vibe coding, when they use vibe coding and don't look at the output, how do they ensure errors don't compound?
As someone who can program and used vibe coding, when they use vibe coding and don't look at the output, how do they ensure errors don't compound?
I'll give you that - you can't vibe code, not look at the output, and push to main of a production codebase. Same as writing code normally.
But you can vibe code and auto-edit your way to a good PR. But you're reviewing the code being output when the agent finishes each task. Maybe that's not pure vibe coding?