poteto@poteto

一直让我挺在意的一点是，有些人把 slop 当成是发生在自己身上的事，好像自己只是个无能为力的旁观者，什么都做不了 不好意思，你可是软件工程师啊，你 literally 学会了怎么让沙子思考、让电脑听你指挥？！现在你却说你对这事没办法？拜托 想穿过这些噪音，你其实只需要知道两件事： 1. 你得给你的 agent 一个能验证自己工作的方式（我刚发过，就不重复了） 2. 你的代码库就是记忆 第 2 点也不是什么新鲜事，我们一直都有 lint 规则、诊断做得好的编译器和强类型系统、LSP 等等，帮我们写出更好的代码。写代码的人换成 agent 也没什么不同，你只是需要更多、更强的这些。 先别管 rules 和 skills，这些以后再加。 是的，你的代码库对 agent 来说就是一种记忆！agent 特别喜欢在已经存在的东西上继续扩展。所以你见过的每一个小毛病、每一个烦人的点，你从 agent 身上看到的每一个错误和坏模式，都得变成一条约束，否则 agent 就会像病毒一样在你的代码里不断重复同样的错误。然后你不断观察、不断重复这个过程，直到你的代码库被锁得足够紧，哪怕是上下文很少的 agent 也能一发打出一个高质量的 PR。 更好的方向是重构/重写你的代码，让 agent 的反模式在类别上就不可能发生。把类型系统用起来，用那些能缩小架构搜索空间的库/框架，或者干脆像我们给 grok bot 做的那样，自己造一个框架，设计高质量的底层原语和想清楚的 API

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