我之前对在全新项目中使用 vibe coding 的看法是错误的。
2 分•作者: dokdev•3 个月前
我过去认为“氛围式编码”对全新项目有益。我错了。
如果你不在乎代码，只想测试你的想法，那它仅仅是一个可抛弃的概念验证，而不是一个项目。是的，氛围式编码非常适合这种情况。
然而，随着时间的推移，工具和模型变得越来越好，智能体开始更好地在现有代码库上工作。很多时候，智能体会发现代码库中现有的方法/代码风格，并据此开始编码。
我意识到，在一个全新项目中，在盲目地交给 AI 之前，重要的是先设定数据模型、数据流和代码库的整体结构。否则，它会变成一个无法维护的混乱，你永远不想再看那段代码。
查看原文
I used to think that vibe coding was good for greenfield projects. I was wrong.<p>If you don't care about the code and all you want to do is just to test your idea, then it is merely a throw-away PoC not a project. And yes, vibe coding is great for that.<p>However, as harnesses and models got better over the time, agents started working better on existing codebases. Often times, agents discover existing approaches/code style in the codebase and they start coding accordingly.<p>I realized that in a greenfield project it is important to set the data models and data flow and general structure of the codebase before handing it off to AI blindly. Otherwise it becomes an unmaintainable mess, and you never want to look at that code again.