HackerNews中文版

我正在尝试了解“氛围编码”在今天的实际情况。我目前正在进行的项目接近6万行代码，业务逻辑相当复杂。根据我所听到的，在这个规模下，只有少数工具（比如Claude的桌面应用）真正有帮助，所以我没有尝试过其他的AI编码服务。与此同时，我不断看到有人在一个40小时的周末里构建出2万行代码并推出SaaS。这让我开始怀疑自己是否过于谨慎，或者只是基于过时的假设在运作。我已经相当依赖AI，一个明显的好处是我现在理解了之前写的代码库中的一些部分，而当时并没有完全掌握。不过，以我目前的进度来看，我感觉还需要几个月的开发时间，再加上几个月的测试，才能将其变成真正的生产服务。而且，这个测试似乎并不是可选的。与此同时，被描述为“氛围编码”的产品似乎并没有受到特别负面的评价。所以我在想，大家现在是如何看待这个问题的。“你并不真正理解代码，所以这会在后面给你带来麻烦”这个批评是否仍然有意义？还是说我们已经到了一个需要改变构建软件默认方法的时刻？我特别希望听到在更大或更复杂系统上工作的人的观点。

查看原文

I’m trying to understand where “vibe coding” realistically stands today.The project I’m currently working on is getting close to 60k lines of code, with fairly complex business logic. From what I’ve heard, at this scale only a few tools (like Claude’s desktop app) are genuinely helpful, so I haven’t experimented much with other AI coding services.At the same time, I keep seeing posts about people building 20k lines of code and launching a SaaS in a single 40-hour weekend. That’s made me question whether I’m being overly cautious, or just operating under outdated assumptions.I already rely on AI quite a bit, and one clear benefit is that I now understand parts of the codebase that I previously wrote without fully grasping. Still, at my current pace, it feels like I’ll need several more months of development, followed by several more months of testing, before this can become a real production service. And that testing doesn’t feel optional.Meanwhile, products that are described as being “vibe coded” don’t seem to be getting particularly negative evaluations.So I’m wondering how people here think about this now. Is “you don’t really understand the code, so it’ll hurt you later” still a meaningful criticism? Or are we reaching a point where the default approach to building software itself needs to change?I’d especially appreciate perspectives from people working on larger or more complex systems.

请问HN： “氛围编码”发展到什么程度了？