CharlieKey takeaways from your favorite podcasts
← 7 October 2026The Pragmatic Engineer

Building resilient systems with Sam Newman

Sam Newman argues resilient systems come from a few simple rules, honest trade-off conversations with the business, human collaboration and clear definitions of good, with AI used cautiously within modular boundaries.

Watch on YouTube ↗

Charlie's summary

  1. Programming is a shared theory in people's minds, not typing, and code is a side effect of how a team works together

    Sam recalls Martin Fowler's line that “programming is not typing” and Peter Naur's idea of a program as a theory living in developers' minds. Code is one mechanism for delivering the system, and speeding up code writing just moves the bottleneck elsewhere. Sam argues AI doesn't change that software is a collective endeavor.

    ▶ 16:39
  2. Microservices are an “architecture of last resort”, worth adopting mainly for organizational autonomy

    Sam defines microservices by independent deployability, with boundaries drawn around the business domain. Because they push you toward distributing state aggressively, you need a good reason. The best one is wanting autonomous teams, and microservices are a means to that end. Sam says people go wrong by expecting other magic stuff to happen. He saw this in enterprises with many developers and little getting done.

    ▶ 29:12
  3. Production is truth: ask where the truth of your system lives, in code, spec, or people's heads

    Channeling his friend Charity, Sam says production is the truth and everything else is a lie we tell ourselves. For what the system should do, teams now sit on a spectrum from code to spec. Sam says specs could become the source of truth, but only if tacit knowledge gets unpacked into them and teams still collaborate. He asks every team to name where their truth lives.

    ▶ 35:41
  4. You can't hand work to agents unless you can define what good looks like and verify it

    Sam notes that most speakers at a spec-driven development conference he ran said you can't do this without defining good. He is fine with a firm dropping human code review if it spends that time on design-level thinking. But if you stop reading code and also stop caring about the rest, “you deserve everything that's going to happen to you.” Expertise is still needed, just at a different place.

    ▶ 40:25

Give your email to unlock the rest of the key points — for every episode.

Do more with Charlie

Free — sign in with your email, no password.