If you’ve ever opened Chrome DevTools, or optimized a page for Core Web Vitals, you’ve used software built by
@addyosmani.
Timestamps:
00:00 Intro
02:50 Addy’s current workflow
05:11 Addy’s path into tech
15:04 Addy’s work on jQuery
16:44 TodoMVC
21:44 Getting hired at Google and working on Chrome
27:17 Building dev tools
40:15 Core Web Vitals
45:42 Google’s engineering culture
51:03 Addy’s career trajectory at Google
57:55 The director role at Google
1:01:40 Cognitive debt and cognitive surrender
1:03:03 Working with agents
1:05:52 Loop engineering
1:12:55 The changing role of the software engineer
1:18:15 How Addy uses AI in writing
1:27:40 What’s next for Addy
1:28:47 Career advice
Brought to you by:
•
@AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. Teams like Jane Street, and the etcd community use Antithesis to ship better code, faster.
•
@sentry – application monitoring software considered “not bad” by millions of developers.
• Google Cloud Run – run untrusted agent code without the security anxiety. Cloud Run sandboxes deliver hyper-isolated, ephemeral execution environments that spin up in milliseconds. Check them out:
Here's Addy's advice on where he believes engineers should invest efforts, in the coming years, in his words:
“What we are very likely to see happen next with engineering careers (as well as product and other roles) is the unbundling of them, so that an engineer also has product sense, while a product person also has engineering sense, or UX sense.
You should think about the non-engineering things if you don’t [usually] have the time to think about product or technical evangelism, or go-to-market approaches, or any other parts of how businesses are successful.
If you can show employers that you are not just a builder, but someone that can help them as roles start to become a little bit fuzzier, then I think that you can be successful in these times.
Don’t be just an engineer.”