When things go wrong in production, how fast can you get back? This episode breaks down rollback strategies as a core design discipline — not a last resort — covering blue-green deployments, canary releases, feature flags, and the habits that make recovery routine.
Most engineering teams treat rollback as a break-glass emergency — something to reach for when everything else has failed. This episode of Automatic.co makes the case for a fundamentally different approach: reversibility is a design requirement, not a rescue plan. Drawing on the rollback strategies deep-dive from the Automatic.co blog, the conversation unpacks the principles, patterns, and practices that separate teams who sleep through incidents from those who are still firefighting at sunrise.
Here's what this episode covers:
The throughline is straightforward: speed matters during an incident, but speed without discipline is just a faster mistake. The episode closes with a call to treat reversibility the way you'd treat any other reliability attribute — build it, test it in daylight, and measure it continuously so that when the moment arrives, pressing undo is a quiet, confident action rather than a frantic one. For more on related failure modes in data systems, check out the earlier episode Schema Evolution: The Silent Breaking Change.
Agentic AI and automation from the perspective of whoever has to maintain it in six months. Where an agent genuinely belongs in a process, where a plain script is enough, how to design a handoff to a human, and what breaks quietly at scale.
Each episode takes one automation decision and reasons it through end to end — including the maintenance burden, the failure modes and the honest question of whether the process should exist at all. Written for operators and technical leads, deliberately free of hype. Five or six minutes an episode.
Topics include where an agent belongs versus a plain script, designing human handoffs, error handling and observability, maintenance burden, process mapping before automation, measuring what a workflow saves, and knowing when a process should be deleted instead.
Produced by Automatic.co, agentic AI and automation consulting. Full details, services and further reading at https://automatic.co