一龍馬/AI 情報站讀懂消息背後的脈絡
星期日
搜尋

Addy Osmani 提出一套把 Agent 程式碼送進正式環境前的控管方法:先定義成果與不可觸碰的範圍,再提供明確的建置、測試、lint、端對端與 schema 檢查

中文摘要

他主張依變更的影響範圍調整審查深度,涉及金流、身分驗證或使用者資料時標準應高於人工作業,並把每次失誤整理成 CLAUDE.md 規則或可重用技能。

一龍馬判讀

工程團隊的重心會從逐行產碼轉向設計限制、驗證流程與累積組織知識;這是實務建議而非成效研究,仍不能取代資安審查與人工責任歸屬。

原文節錄

Addy Osmani · @addyosmani

Your job is the design and the bar.…

取得全文 · 不代表內容已獨立查證

查看原文
完整收錄文字與來源

How do you hold the bar on production agent code?: 1. Agree on the outcome and the constraints first. What does "done" look like? what must it not touch? is the simpler design is to refactor or reuse what you already have? Then let Claude cook. You do not need a long planning ritual on the latest models. You do need to reject a bad change before it becomes a PR. 2. Give Claude a way to check its work. Put the exact build, test, and lint commands in there. Turn the things you reject in review into skills: /verify, e2e, schema checks and so on. Run those before you open the PR. Use /code-review. I've said that quality now lives in the constraints you put around your agents and think this is worth spending time on. 3. Your job is the design and the bar. Blast radius decides how much you read. Throwaway code with a small blast radius can be a black box. Production code should have a higher bar than if a human wrote it, especially anything that touches money, auth, or user data. 4. When Claude misses, don’t quietly fix it by hand. Have it write the lesson into CLAUDE.md or a skill. If it still misses, use the latest frontier model, turn effort to higher or have Claude pay down the debt and make the codebase easier to work in. You can start with one check you already run today on every PR. The rest compounds from there.

收錄日期
2026-09-13
來源
Nitter RSS(公開貼文)
抓取時間
2026/09/13 10:46(台北)