Couverture de The Pragmatic Engineer

The Pragmatic Engineer

The Pragmatic Engineer

De : Gergely Orosz
Écouter gratuitement

Software engineering at Big Tech and startups, from the inside. Deepdives with experienced engineers and tech professionals who share their hard-earned lessons, interesting stories and advice they have on building software. Especially relevant for software engineers and engineering leaders: useful for those working in tech.

newsletter.pragmaticengineer.comGergely Orosz Politique et gouvernement
Épisodes
  • From Chrome DevTools to AI Engineering, with Addy Osmani

    From Chrome DevTools to AI Engineering, with Addy Osmani
    Aug 19 2026
    Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• Google Cloud Run – run your code and host LLMs directly on top of Google’s scalable infrastructure, without having to worry about managing infra.• Sentry – application monitoring software considered “not bad” by millions of developers—Addy Osmani spent more than 14 years at Google, working on Chrome, DevTools, Core Web Vitals, and most recently, AI developer experience.If you've ever opened Chrome DevTools, or optimized a page for Core Web Vitals, you’ve used software built by Addy Osmani. In this episode, I sit down with Addy and we talk about his path from building a web browser aged just 16 to becoming a director at Google. We discuss what he learned from building tools for millions of developers, Google’s engineering culture, and why he continued doing hands-on coding work as a manager. We also get into how he works with AI agents today, the risks of ‘cognitive surrender,’ his approach to ‘loop engineering,’ and why it’s good to develop skills in product management, go-to-market, and other areas.—Timestamps00:00 Intro02:50 Addy’s current workflow05:11 Addy’s path into tech15:04 Addy’s work on jQuery16:44 TodoMVC21:44 Getting hired at Google and working on Chrome27:17 Building dev tools40:15 Core Web Vitals45:42 Google’s engineering culture51:03 Addy’s career trajectory at Google57:55 The director role at Google1:01:40 Cognitive debt and cognitive surrender1:03:03 Working with agents1:05:52 Loop engineering1:12:55 The changing role of the software engineer1:18:15 How Addy uses AI in writing1:27:40 What’s next for Addy1:28:47 Career advice—The Pragmatic Engineer deepdives relevant for this episode:• What is loop engineering?• Inside Google’s engineering culture• How AI-assisted coding will change software engineering: hard truths• Are AI agents actually slowing us down?• How Claude Code is built• How Codex is built• From IDEs to AI Agents with Steve Yegge• Google’s engineering culture: the podcast—Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    Afficher plus Afficher moins
    1 h et 32 min
  • Stop being skeptical about AI for development with Charity Majors

    Stop being skeptical about AI for development with Charity Majors
    Aug 12 2026
    Brought to You By:• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• WorkOS – everything you need to make your app enterprise ready.• Buildkite – CI software built to absorb whatever your coding agents throw at the build queue—In 2025, it was rational to be skeptical about AI, but in 2026 it’s clear that AI is changing all of the industry, and there’s less and less place for skepticism. This take is from one of my favorite voices in software reliability and observability: Charity Majors, CTO and cofounder of Honeycomb, co-author of Observability Engineering. (Note: the second edition of Observability Engineering is out, and it’s pretty much a full rewrite of the book, I recommend grabbing it if you’re building reliable systems)In this episode, I sat down with Charity to discuss how her thinking on AI has evolved, why she believes it is becoming a foundational part of software engineering, and what that means for how teams build, review, and ship software.We explore how AI is changing the economics of code generation, why reliability and verification are increasingly the bottlenecks, and why the rise of non-deterministic systems requires more engineering discipline. Charity shares her views on code reviews, observability, DevOps, leadership, and why both AI skeptics and enthusiasts are getting important things right.—Timestamps00:00 Intro02:56 How Parse led to Honeycomb06:00 The limits of individual productivity metrics09:08 How Charity’s perspective on AI has evolved13:50 Rewriting code vs. editing code19:20 Production as a stage of development22:14 Code reviews26:56 Non-deterministic systems31:11 Sensible uses of AI37:41 The two AI camps44:40 Why AI works so well for building software49:42 DevOps55:13 Modern observability1:00:40 Handling context overload1:01:56 What’s new in Observability Engineering’s 2nd edition1:07:45 What effective leadership looks like1:10:25 Engineering management: what is changing?1:16:31 Junior engineers1:18:01 AI fatigue1:21:39 Book recommendations—The Pragmatic Engineer deepdives relevant for this episode:• Shipping to production• Deepdive: How 10 tech companies choose the next generation of dev tools• Why is Meta destroying its engineering organization?• When AI writes almost all code, what happens to software engineering?• Are AI agents actually slowing us down?• Observability: the present and future, with Charity Majors• The third golden age of software engineering – thanks to AI, with Grady Booch—Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    Afficher plus Afficher moins
    1 h et 26 min
  • Formal methods with Hillel Wayne

    Formal methods with Hillel Wayne
    Jul 29 2026

    Brought to You By:

    • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.

    • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.

    • WorkOS – everything you need to make your app enterprise ready.

    —

    There’s a popular theory that AI will finally make formal verification mainstream because mathematical proof of correctness will be needed when machines write most or all of the code. But will this happen? Today, I’m talking with one of the best people to tackle the prediction. Hillel Wayne is a formal methods consultant, educator, and author, who’s deeply interested in software history.

    In this episode of Pragmatic Engineer podcast, I sit down with Hillel to compare software engineering with traditional engineering, discuss where formal methods fit into modern software development, and we explore why they are essential for some of the world's most complex systems. We cover the formal specification language, TLA+, walk through several formal verification tools, examine why distributed systems are so difficult to reason about, and look into whether AI will make formal methods accessible to more engineering teams.

    —

    Timestamps

    00:00 Intro

    03:21 The Crossover Project

    10:26 What software engineering does better

    14:19 What traditional engineering does better

    17:06 Formal methods

    28:21 TLA+: what it is and demo

    35:47 TLA+ at Amazon

    36:59 Ways distributed systems break

    39:52 Formal methods and systems thinking

    45:09 The value of learning math

    49:12 What TLA+ is good for and isn’t

    51:39 Alloy: a declarative language for software modeling

    57:42 Other formal methods tools

    1:00:13 Property-based testing

    1:04:20 AI and the need for formal verification

    1:11:18 Logic for programmers

    1:13:24 Hillel’s 2025 prediction on AI’s impact

    1:20:19 Book recommendation

    —

    The Pragmatic Engineer deepdives relevant for this episode:

    • How to debug large, distributed systems: Antithesis

    • How AWS S3 is built

    • Paying down tech debt

    • How Big Tech does quality assurance (QA)

    • Bug management that works

    • Resiliency in distributed systems

    —

    Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.



    Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    Afficher plus Afficher moins
    1 h et 24 min
adbl_web_anon_alc_button_suppression_t1
Aucun commentaire pour le moment