Hard disagree. Usually I am wiser than the AIs but there have been times where the AI has pushed back and made me see the light on some poor design I was about to pursue
I think the issue here is the nebulous definition of vibecoding.
You, as an experienced engineer, are doing a lot of hand holding and review of LLM-generated output, maybe even(?) using it as purely a check on your own work. There are others, though, that are essentially outsourcing the entire process to a basic, underspecified chat prompt.
It's a mix. There are some projects where I let the LLM mostly run free and I focus on architecture. Even through some scary parts. Recently I picked a parallelization scheme for this and let the LLM cook. I have no idea how it implemented it, except that it (supposedly) "does it the way I asked:
dnautics · · focus · HN ↗
bjord · · focus · HN ↗
You, as an experienced engineer, are doing a lot of hand holding and review of LLM-generated output, maybe even(?) using it as purely a check on your own work. There are others, though, that are essentially outsourcing the entire process to a basic, underspecified chat prompt.
dnautics · · focus · HN ↗
<a href="https://github.com/ityonemo/bpa" rel="nofollow">https://github.com/ityonemo/bpa
For my projects that I use day to day in prod there is considerably more hand-holding and code review.