poteto@poteto

我们得重建、重写大量软件，去适应一种全新的、更快的节奏。 以前代码是一滴一滴来的。很快（如果现在还没有的话），代码会像一股连续不断的水流一样被写出来，像一条狂暴的河，想怎么拐就怎么拐。 这不是什么新鲜事：大厂早就因为工程团队规模巨大而不得不面对这个问题。但现在 ai 给每个工程师都配上了一支弹性极强、能力超强的劳动力。这现在是你的问题了，唯一的适应办法就是进化你的系统，让 agent——即使是、尤其是那些不太了解正确做法的 agent——也能如鱼得水。让简单的做法就是正确的做法。 你的代码库正在变成有机建筑。agent 的贡献会围绕你设计的约束和护栏生长。好的软件工程现在更重要了！而且不，这股连续不断的代码流不是你只能无助旁观的东西。野心大一点，去设计能驾驭混乱的系统、框架和语言。 为写代码哀悼的时候早就过去了

we will need to rebuild and rewrite much of software to adapt to a new, faster pace. code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases. this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing. your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails you’ve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos. the time for mourning coding is long over