代码腐烂没有下限，业务先死
推荐指数 32.0 NO. 016 · 2026.09.06
发布2026/09/05Score95Comments77
为什么值得看
作者以亚马逊订单系统经历为例，指出"沉船"等比喻误导了技术债的本质——代码不会自动停止恶化，企业倒闭才是终点。对AI工程师的警示：烂代码的代价是持续累积的复利，而非可预测的一次性事件。
编辑判断
这篇文章戳破了一个行业幻觉：很多团队把重构排进"下个季度"，本质上是相信存在一个"还能用的底线"。但作者亲历的亚马逊订单系统证明，烂代码会不断自适应地长出新的耦合层，最终维护成本曲线是指数而非线性。
对AI从业者尤其值得警惕——当前大量AI工程代码处于"能跑就行"的草莽期，LLM调用链、提示工程、RAG管线的快速迭代正在制造前所未有的技术债密度。建议现在就开始建立AI特有代码的lint规则和回归测试，而不是等模型版本混乱到无法追踪时再补救。
社区反馈
负面 69 条评论
核心争论：LLM生成代码是否正在加速技术债累积，成为新一代'外包代码'灾难
If you have ever worked with low-cost offshore contractors, you know this it true…
So true. I worked one place where I had a team of 4 offshore devs replace my two good people. Three months of some of the worst quality work I’ve ever seen. And I was responsible for it on paper. Decided fuck it, promoted one of them to manager and gave him a project to finish in 3 months, leading t
A lot of people are going to get a painful lesson in this if companies keep using LLMs to do all their programming.