“Most likely better” is carrying a lot here. Risk matters to my customers and having a 1% chance of erasing a production DB or inserting a typo squatting malicious dependency that exfiltrates and enables ransomware is not acceptable for those customers. They don’t care how you built it, but they do care that you know how it’s really built which is antithetical to vibe coding. Vibe coders can be very smart, but they are in “trust, don’t verify” mode.

this is completely unrelated to the article, which is about not _enjoying_ vibecoding. even if I agreed with you, I would still think commenting this on this article is a real dick move