>>941651576
the inventor of the term "vibe coding" doesn't even vibe code his own projects.
In my experience it's only good for writing unit tests and helping refactor small chunks of code and autocomplete. Anything that needs context beyond the immediate project (so pretty much anything enterprise grade unless you're operating in a shitty monolith) is a no go.