Don't Build Agents You Can't Explain
addyosmani · x · 2026-07-16
In his closing keynote, Addy Osmani emphasized: do not build Agents you cannot take responsibility for explaining.
Key points include:
- Roles/titles < system ownership: Rather than giving someone an "AI-flavored" job title, it is more important to clarify who is accountable for the system's outcomes.
- Quoting Mitchell Hashimoto: when the "speed of generation" exceeds the "speed of understanding," the scarce resource becomes evidence-based judgment.
- His proposed new rule is: "Explain it, or don't ship it."
The post focuses less on specific tools and more on accountability, judgment, and explainability in Agent products and team practices.
Related event: Addy Osmani: Engineers Must Be Accountable for Agent Systems(3 posts)→
More from coding & agent
- Dev turns DJI Mavic into local AI security drone built with Opus 5.5 — alexcovo_eth · 2026-10-27
- Microsoft Research: ForkPilot cuts long-horizon agent compute by up to 59% — EliasEskin · 2026-10-27
- Cursor launches Agent SDK: agents as code with Markdown prompts and TypeScript tools — soleio · 2026-10-27
- Vibecheck, the 'usable formal methods' hackathon, sells out two floors in SF — spikedoanz · 2026-10-27
- How do you verify AI agent outputs beyond unit tests and LLM-as-judge? — Practical_Green5775 · 2026-10-27
- AI agents may soon become the only way to run code, not just write it — IgorCarron · 2026-10-27