Where vibe coding fails is in producing maintainable code for production settings. I firmly believe that as a developer you have to take accountability for the code you produce - if you're going to put your name to it you need to be confident that you understand how and why it works - ideally to the point that you can explain it to somebody else.

Vibe coding your way to a production codebase is clearly a terrible idea. Most of the work we do as software engineers is about evolving existing systems, and for those the quality and understandability of the underlying code is crucial.

For experiments and low-stake projects where you want to explore what's possible and build fun prototypes? Go wild! But stay aware of the very real risk that a good enough prototype often faces pressure to get pushed to production.

If an LLM wrote every line of your code but you've reviewed, tested and understood it all, that's not vibe coding in my book - that's using an LLM as a typing assistant.

受限于目前 LLM 的 ability 和 context window，Vibe Coding 更适合功能明确的一次性 App，如果涉及到持续迭代、调试，作为程序员必须要对代码有足够的了解。如果采用模块化设计，将 LLM 生成的代码「关」在模块内，这样即使生成的代码有问题，影响的范围也有限，而且也方便定位。