Vibe Coding 正在制造技术巴别塔
推荐指数 34.0 NO. 018 · 2026.07.15
发布2026/07/14Score139Comments45
为什么值得看
作者将 Vibe Coding 导致的软件随机失控，类比为《圣经》中巴别塔的建造困境：技术迭代（砖与泥）本应推动文明进步，但最终瓦解的是协作共识而非工具本身。对 AI 工程师的警示是：当生成式开发让代码变更不可预测时，团队层面的"共同语言"比技术栈更脆弱。
编辑判断
HN 评论区有个被忽视的共识分裂：一派认为 Vibe Coding 的混乱是可控的，只要加强 prompt 规范和代码审查；另一派则认为这是根本性的范式冲突——当 AI 生成的代码连作者自己都无法完全解释时，传统 code review 机制已经失效。
更值得警惕的是组织层面的信号。已经有团队开始用"vibe 产出"和"传统产出"双轨并行，实际上是在用政治手段解决技术问题。如果你在管理 AI 原生团队，需要明确一个规则：哪些模块允许 vibe（原型、内部工具），哪些必须保留可审计性（核心逻辑、数据管道），模糊的中间地带会消耗最多的隐性成本。
社区反馈
负面 45 条评论
核心争论：AI 加速代码产出但摧毁团队协作所需的系统理解，个体效率提升与集体维护成本失衡
相关内容
It used to be that you need a good reason to make huge refactorings, because it’s often so much work. Now agent can rewrite half of your code if your prompt is vague enough and you don’t actual try to review it all. And so the “soul” of a program can change dramatically every single day. It’s both g
The biggest obstacle to huge refactoring has always been minimizing the risk of bugs, not losing any features, and ensuring compatibility with the existing ecosystem. The reason it's become easier in the age of AI is because we stopped caring about these things.
Yep. That’s what people are forgetting. If you have an application that many people depend on to do real work, to make money, you won’t survive if you allow AI to constantly make huge changes. Your test suite doesn’t cover all workflows. It doesn’t cover every combination of actions a user can take.