About this episode
Patrick Debois: Organised the first DevOpsDays in Ghent in 2009 and co-authored The DevOps Handbook. Today he is an independent advisor and Product DevRel Lead at Tessl.
What to take away
- Most factory products automate the same loop of writing, reviewing and deploying code. What sets one apart is how it decides which change ships without a human review, and architecture absorbs part of that risk.
- Turn whatever you can into deterministic checks. Teams that start with a loose orchestrator usually end up with something close to a state machine.
- Judge a factory by two numbers: how many human touches a process still needs, and how much of the factory's work the rest of the organisation reuses.
Chapters
- (opens in a new tab) Intro
- (opens in a new tab) Software Factories Through a DevOps Lens
- (opens in a new tab) Risk Is the Real Merge Decision
- (opens in a new tab) Dark Factories Come in Gradations
- (opens in a new tab) Orchestrators vs. State Machines
- (opens in a new tab) Research Loops and the Dream Factory
- (opens in a new tab) Smaller Teams, Fused Roles
- (opens in a new tab) Factories as Platforms
- (opens in a new tab) What Happens to Juniors?
- (opens in a new tab) Two Metrics for a Software Factory
Host and guest
Mentioned in this episode
Transcript
Benedikt Stemmildt
Moin moin, and welcome back to another episode of Rethink Engineering. This is a very special one for me because we discuss a lot of the topics why we renamed the podcast with our guest today. I'm Benedikt, I'm the co-founder of hackers&wizards. We teach engineering teams how to work with agents and factories and this show here is powered by us and also by re:cinq.
Patrick Debois
As they say, moin moin. No, I don't know what to say. This is how you always greet me. So thanks for having me, Benedikt, on the show.