提问 HN：遗留代码库维护的未来走向？
1 分•作者: AnnKey•6 个月前
最近我看到一些传闻，说有人在遗留代码库中使用 Claude Code，在相对较少的监督下就能解决复杂问题。甚至有人声称 Claude Code 能够编写大部分代码，而且他们不再需要指导新员工——取而代之的是，AI 回答他们的问题，他们可以在最初的几天内开始进行有意义的修改。这听起来好得难以置信，所以我很想了解一下真实情况。
我职业生涯的大部分时间都花在遗留代码库上，阅读、追踪行为、小心翼翼地进行修改，并编写测试来保护它们。不过，我休了长假，很快就要结束了，我对这段时间发生的事情感到既担忧又兴奋。
对于那些正在处理遗留代码库的人来说：
* 工作流程真的已经转变为提示 AI、审查输出和维护 .md 说明了吗？
* 你们公司允许使用 Claude Code、Codex 或类似的工具吗？如果不行，你们用什么？
* 公司是否担心成本和代码隐私问题？
* 你认为一年后会发展成什么样子？
具体的例子，无论是好的还是坏的，都将特别有帮助。谢谢。
查看原文
I've seen a few anecdotes lately that say that they use Claude Code on legacy codebase and with relatively little supervision it can work on complex problems. Then the claim that Claude Code writes most of its own code, and that they no longer mentor their newcomers - instead, AI answers their questions and they can start making meaningful changes within the first few days. To me it sounds almost too good to be true, so I'd love to have some reality check.<p>I've spent most of my career in legacy codebases, reading, tracing behavior, making careful changes, and writing tests to protect them. I've taken a sabbatical though, which ends soon, and I'm quite worried and excited to what has happened during this time.<p>For those working on legacy codebases:<p>- Has the workflow really shifted to prompting AI, reviewing output, and maintaining .md instructions?<p>- Does your company allow Claude Code, Codex or similar tools? If not, what do you use?<p>- Do companies worry about costs and code privacy?<p>- Where do you think this is headed, a year from now?<p>Concrete examples, good or bad, would be especially helpful. Thanks.