问HN：氛围编程在实际工作或运营产品/服务中可行吗？
我到处看到对“氛围编码”的赞誉，因此我自己也尝试了几次。虽然它在简单脚本或原型上效果不错，但当复杂性增加或需要更实质性的东西时，似乎就会遇到明显的局限性。我是不是漏掉了什么？我很想听听大家的经验。
作为背景，我的尝试在简单的自动化任务和快速原型方面是成功的，但当我试图构建更复杂的系统或需要强大错误处理、可维护性或与现有代码库集成的任何东西时，这种方法就显得不足。生成的代码往往缺乏生产系统所需的架构考虑和边缘情况处理。
有没有人成功地将这种方法用于严肃的开发工作，还是说它主要是一个用于快速原型和学习的工具？你们在将AI辅助编码扩展到简单任务之外的经验如何？
查看原文
I keep seeing praise for vibe coding everywhere, so I’ve tried it myself a few times. While it works fine for simple scripts or mockups, it seems to hit clear limitations when complexity increases or when you need something more substantial. Am I missing something here? I’d love to hear your experiences.
For context, my attempts have been successful with straightforward automation tasks and quick prototypes, but when I’ve tried to build more complex systems or anything requiring robust error handling, maintainability, or integration with existing codebases, the approach falls short. The generated code often lacks the architectural considerations and edge case handling that production systems require.
Has anyone successfully used this approach for serious development work, or is it primarily a tool for rapid prototyping and learning? What’s been your experience with scaling AI-assisted coding beyond simple tasks?