Addy Osmani is the enterprise-hands-on voice on agentic engineering, a 14-year Google engineering leader (most recently Director at Google Cloud AI) who writes practitioner-level guidance on coding agents, harnesses, evals, and the engineering discipline that keeps agent output maintainable. Facts below verified as of 2026-09-13.
He fills the enterprise-hands-on niche: where indie practitioners show what an agent can do and org analysts measure adoption, he writes from inside a hyperscaler about holding agent-built software to a production quality bar.
What it is #
A personal blog, books, and open-source repos by Addy Osmani, an engineering leader who spent over 14 years at Google, led developer experience across Chrome and then Gemini’s developer experience, and served as a Director at Google Cloud AI running Cloud AI Developer Experience and Technical Evangelism before departing Google in 2026 after 14 years. His stated current focus is agentic engineering: coding agents, harnesses, evals and benchmarks, and code quality. His 2026 essays carry concrete theses, like “Agent Skills” (2026-05-03), which argues that the senior engineer’s real job is the parts that do not show up in the diff, specs, tests, reviews, and refusing to ship what cannot be verified. He packages that argument into artifacts teams can adopt, notably the “Beyond Vibe Coding” book and the production-grade agent-skills repository.
Status #
Active and high-reach as of 2026-09-13. “21 Lessons From 14 Years at Google” (2026-01-03) reached 1,678 points on Hacker News, “Agent Skills” 376 points, and “The next two years of software engineering” (2026-01-11) 328 points. He discussed “Beyond Vibe Coding” and enterprise AI engineering practice on The Pragmatic Engineer (2025-10-29).
Strengths #
- He writes the leader-plus-practitioner view: verification discipline, review throughput, and scope control around agents, not just demos.
- His claims come from running AI developer experience at Google, so enterprise-scale failure modes like unverifiable output and skill atrophy are first-hand observations.
- The advice ships as artifacts: his agent-skills repository turns the essays into working skills other teams can install and adapt.
- He is willing to argue against the flow, as in “Don’t Outsource the Learning”, which pushes back on letting agents erode engineer growth.
Cautions #
- The vantage point is Google-scale, so budgets, tooling, and talent density most teams cannot match sit underneath the advice.
- He was an evangelist by role at Google, and the advocacy for the AI engineering programs he ran there is inseparable from the writing.
- The leader’s perspective means less terminal-level detail than the indie hands-on voices.
- The Hacker News discussion of his work shows real pushback that his frameworks can read as boilerplate, so treat the essays as positions to test, not checklists.
Pricing #
Free to read. His books are sold commercially, while “Beyond Vibe Coding” has a free online edition.
Compared to #
- Simon Willison: both are hands-on, but Willison experiments as an indie while Osmani reports from inside enterprise constraints and leadership accountability.
- The Pragmatic Engineer: Orosz surveys the org layer across companies from the outside, Osmani shows one enterprise’s practice from the inside.
- Hamel Husain: Husain goes deep on the evaluation loop itself, Osmani on the engineering system and team discipline around agents.
Bottom line #
Recommended for engineers and leads inside established companies who need enterprise-grounded, hands-on agentic engineering practice rather than indie experiments or vendor marketing. Not for readers wanting frontier research depth or a terminal-level tool feed.
Changes #
- 2026-09-02 - Created in the People and publications category, filling the enterprise-hands-on gap the matrix named.
- 2026-09-12 - Reframed around his departure from Google in 2026 after 14 years.
See also #
- Agentic Coding Tools Landscape - the tool layer his quality-and-discipline argument wraps around
- Rethinking Code Review in the Age of LLMs - the review role his “parts that do not show up in the diff” thesis depends on
- The Codebase Gardener - the long-term codebase stewardship his maintenance-first framing serves
References #
https://addyosmani.com/ - his site and stated focus on agentic engineering and AI-assisted development
https://addyosmani.com/bio/ - role history: Chrome developer experience, Gemini developer experience, Director at Google Cloud AI
https://addyosmani.com/blog/agent-skills/ - the “Agent Skills” essay and its verification-discipline thesis
https://addyosmani.com/blog/next-two-years/ - his 2026 view of where software engineering is headed
https://addyosmani.com/blog/21-lessons/ - the 14-years-at-Google retrospective, his highest-reach essay
https://newsletter.pragmaticengineer.com/p/beyond-vibe-coding-with-addy-osmani - independent interview on “Beyond Vibe Coding” and enterprise practice
https://beyond.addy.ie - the “Beyond Vibe Coding” book site (the old vibe.addy.ie reference was the separate Bolt vibe-coding guide)
https://github.com/addyosmani/agent-skills - the production-grade agent skills repository
https://news.ycombinator.com/item?id=48015397 - the critical Hacker News discussion of the “Agent Skills” thesis