About this episode
Sam Newman: Independent consultant and author of Building Microservices. His new book is Building Resilient Distributed Systems.
What to take away
- Automated remediation with AI is a long way off. Where it helps today is the moment a person has to work out what is going on, provided production sends good signals.
- Teams that own their domain should decide where a software factory fits, with enabling and platform teams behind them, instead of following a corporate mandate.
- Do not hand a factory your whole system. Take one less critical module behind a service boundary that people still own, and try specs there first.
Chapters
- (opens in a new tab) Intro
- (opens in a new tab) Sam's New Book on Resilient Distributed Systems
- (opens in a new tab) Making Sure Things Go Right
- (opens in a new tab) Robustness and Rebound
- (opens in a new tab) LLM Providers Aren't Cloud-Grade Yet
- (opens in a new tab) Why AI Auto-Remediation Is a Long Way Off
- (opens in a new tab) Rabbits, Burning SSDs and the Unexpected
- (opens in a new tab) Is a Software Factory Resilient?
- (opens in a new tab) Teams, Not Top-Down AI Mandates
- (opens in a new tab) Ship Fast Enough to Care
Host and guest
Mentioned in this episode
Transcript
Benedikt Stemmildt
Good morning, everyone. Welcome back to Rethink Engineering. I am Benedikt, your host of this show, and in this podcast, we try to explore how agentic engineering has a profound effect on the teams that deliver software and on your organization. The show is powered by hackers&wizards and re:cinq, and today we are going to talk with Sam Newman. You probably know him because he wrote a lot of books on building microservices, and he now wrote a book about resilience in distributed systems.
Benedikt Stemmildt
Hello, Sam. Welcome to our podcast. I'm super honored to have you here. How are you doing these days? What are you doing? Who are you? Maybe you introduce us a little bit into your current world.