From Normalizing Complexity to Recognizing the Price
summary
Most teams normalize Monday morning threads about stuck payouts, manual retries, and broken cleanup jobs and end up building five independent background jobs to paper over one process. The claim: that cost compounds into lost product velocity and manual runbooks; the fix shown is orchestration with durable workflows (Temporal is the example platform), turning a five-step staircase of retries, throttles, routing, dedupe and sweepers into one workflow per payment and eliminating the three people, three dashboards recovery path, sometimes implemented in three hack-day workdays.
AI-written summary · about
chapters (13)
- 0:00Introduction and setup
- 1:08Normalized chaos in systems
- 3:13Why we delay fixing coordination
- 4:17Warning sign one: ordered workflows
- 6:51Warning sign two: you’re the coordinator
- 7:54Warning sign three: load-bearing sweeper
- 8:59Warning sign four: not yet is a decision
- 13:34The orchestration tax we pay
- 17:50What changes with orchestration
- 25:31Four patterns to score your system
- 27:18Making invisible costs visible
- 28:22Key takeaways and call to action
- 29:03Q&A begins
related talks
57mReinventing Operations Transformation
32mStop Automating, Start Investigating: Slow Down 2 Speed Up
17mBeyond DevOps – Holistic transformations in uncertain times
18mWe need to talk about SRE burnout
01h 04mPredictably Unpredictable
01h 02mTools for simplified large scale systems
20mDoing Things the Hard Way
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams