Addy Osmani

@addy-osmani · 22 positions · On ppll ↗

Engineering leader and author who spent 14 years at Google, most of it on Chrome and Chrome DevTools, rising from software engineer to director of engineering, and who created TodoMVC and helped push Core Web Vitals.

Addy Osmani did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

What Addy Osmani says most about

coding agents 5

Working with a coding agent should leave both of you better every day, and that only happens if you deliberately record what was learned and decided in the session.
An agent can tell you whether a thing looks correct against a spec; it cannot tell you whether the thing is any good.

See all 5

design 3

People treat an unresponsive interface exactly the way they treat a slow pedestrian crossing: they keep hitting the button.
Engineering, product and UX roles are converging, so the career advice that matters now is: do not just be an engineer.

See all 3

AI agents 2

Reading every agent trajectory has stopped being possible, and what replaces it is demanding an end-to-end account of the decisions that were made.
Building a system that does the prompting for you is not a break with software history but the next rung on the same ladder of rising abstraction.

See all 2

AI and jobs 2

What engineers will stay valuable for is being answerable for a system — the named person who decides what ships, what is blocked and what is deferred, whoever or whatever wrote the code.
Whatever humans are still better at than models is alpha that decays with every model release, so the skill worth naming today will not be the one worth naming next year.

See all 2

software performance 2

"Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices.
Computing is an onion, and the more layers of it you can peel back and understand, the better you can build for the constrained machines real people are using.

See all 2