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

Addy Osmani 談「軟體工廠」與程式代理時主張,就算 AI 產出的程式碼已可出貨,仍需要人類品味與責任歸屬

中文摘要

他建議人類應提前介入產品意圖、系統設計與品質門檻,並把品質檢查盡量提早、持續地放進流程,例如型別系統、自動化測試、mutation testing、安全掃描與架構 lint。重點不是檢查項目越多越好,而是要找出訊號雜訊比最佳的位置,並保留人類對正式上線內容的 ownership。

一龍馬判讀

這把 AI coding 從「能不能寫」拉回「誰決定可維護、可上線、可負責」,對導入 Claude Code、Codex、Cursor 等工具的工程組織很實際。風險是若只堆工具檢查而沒有產品與架構判斷,反而可能製造流程幻覺。

原文節錄

Addy Osmani · @addyosmani

If you're building a software factory, code good enough to ship still needs human taste and ownership.…

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

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

If you're building a software factory, code good enough to ship still needs human taste and ownership. You'll likely need humans in the loop upfront for deciding on product intent, system design (if you care) and your quality bar. Do review code (lights-on factory) but be intentional with where it's needed the most. I've found you want to watch out for where automated back-pressure breaks. Or where maintainability trade-offs need to be made. Aim for quality checks to happen as early and continuously as possible. Not all of them have to, but this includes type systems, automated tests, mutation testing, security scanners and linting for architecture rules. Number of checks != quality. You'll likely need to experiment with what checks give you the best signal to noise ratio. Be ready to tighten or relax your constraints deliberately. You want to build your factory so some aspects of human taste get encoded in the environment, the agent gives you evidence of its work being right and where a human still "owns" what ships to production.

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