Lauren Tan：代码库就是智能体的记忆
something that keeps bothering me is how some people see slop as something that is happening to them, like they're some kind of helpless bystander powerless to
前 Meta 工程师 Lauren Tan 提出，应对 AI 生成代码泛滥的关键是两点：给智能体自我验证的手段，以及把代码库当作智能体的记忆。她认为 lint 规则、强类型系统、LSP 等约束应转化为智能体的约束，否则智能体会像病毒一样重复同样的错误；更好的方向是重构代码，让智能体反模式在类型系统层面变得不可能，例如为 grok bot 自建框架和高质量原语。
查看原帖the slop conversation is so one sided, it's not just that you can produce more code you can also observe, debug, and refactor more code even if the code is slop you have such good tools to deal with it. even if you write code manually, it's still 100x easier to maintain it
正文
当前显示原文，中文全文译文尚未就绪。
something that keeps bothering me is how some people see slop as something that is happening to them, like they're some kind of helpless bystander powerless to do anything about it
excuse me but you are a software engineer, you literally learned how to make sand think and make computers do your bidding?! and now you can't do anything about it? please
the 2 things you should know to cut through all the noise:
1. you need to give your agent a way to verify its own work (i just posted about this so won't rehash) 2. your codebase is memory
the 2nd is not new either, we have always had lint rules, compilers with good diagnostics and strong type systems, LSPs, etc to help us write better code. there is no difference when agents write the code instead, you just need more of them, and stronger ones.
forget rules and skills. you can add those later.
yes, your codebase is a form of memory to agents! agents love extending what already exists. so every nit and every annoyance you've ever seen, every mistake and bad pattern you observe from agents, needs to turn into a constraint, or the agents will just keep repeating those same mistakes like a virus in your code. then you keep observing and repeating this process until your codebase is locked down enough that even agents with little context can one shot a high quality PR.
an even better direction is to refactor/rewrite your code such that agent anti-patterns become categorically impossible. use type systems to your advantage, use libraries/frameworks that reduce the architectural search space, or heck, create your own framework like we did for grok bot and design high quality primitives and well thought out APIs