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