I disagree with this statement:<p>“If an LLM wrote the code for you, and you then reviewed it, tested it thoroughly and made sure you could explain how it works to someone else that’s not vibe coding”<p>You can have a valid workflow were you vibe-code, and then review it thoroughly, that’s still doing vibe-coding + good software engineering practices, but I still consider it vibe coding.<p>That said, I recognize that maybe we are just debating definitions.<p>But I would like to argue that vibe-coding can be a good coding practice on its own when properly integrated with sound software engineering practices