The bit you're missing is that people who can program also use "auto edits" and "vibe coding" when it fits the problem at hand

▲

stavros a day ago | parent [-]

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?

▲

afro88 12 hours ago | parent [-]

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?

	▲	stavros 8 hours ago \| parent [-]
		The definition of vibe coding is that you aren't looking at the code. That's what's never worked for me.