问HN：‘氛围编码’是软件开发的未来吗？
我一直在思考“氛围编码”对软件开发的影响。
想象一下一个两阶段的方法：首先，业务用户与人工智能编码助手合作，指定并创建功能原型，而无需编写代码（“氛围编码”）；然后，开发人员接手重建并将这些原型投入生产。
这可能会：
- 通过绕过传统的需求收集，加快初始开发速度
- 让业务用户能够直接将他们的需求以可工作的原型形式表达出来
- 使开发人员能够更专注于架构、性能、安全性和复杂功能
- 促进业务团队与技术团队之间更具协作性的关系
这只是一个不理解软件开发运作的普通软件用户的天真想法，还是说这种氛围编码的应用真的能够改变现有的工作方式？
查看原文
I've been thinking about the effects of 'vibe coding' on software development.<p>Imagine a two-phase approach: First, business users work with AI coding agents to specify and create functional prototypes without writing code ("vibe coding"), then developers take over to rebuild and productionize these prototypes.<p>This could potentially:<p>- Speed up initial development by bypassing traditional requirements gathering<p>- Allow business users to directly express their needs as working prototypes<p>- Let developers focus more on architecture, performance, security, and complex features<p>- Create more collaborative relationships between business and technical teams<p>Is this just the naive thinking of a software _user_ who doesn't understand how software development works, or could this application of vibe coding change how things are done?