The myth of set-and-forget automation
Automation isn't a thing you build once and walk away from. The systems that keep working are the ones someone keeps an eye on.
The dream sold with automation is set-and-forget: build it once, and it runs forever while you do something else. The first half is real — automation does run on its own. The 'forever' part is the myth. The world the automation lives in keeps changing, and an unwatched system eventually drifts out of step with it.
The ground shifts under it
APIs change, data formats evolve, the business rules the automation encodes become outdated, volumes grow past what it was built for. None of this announces itself. A set-and-forget automation doesn't fail loudly on day one; it quietly does the wrong thing months later, and nobody notices until the damage shows up.
Forget-but-monitor
The realistic version is automation you don't operate by hand but do keep an eye on — with monitoring that surfaces when something drifts, and someone who owns it. That's a big part of why we stay on after launch. Automation is a living system, not an appliance you install and ignore.
Set-and-forget is half true. It runs without you; it doesn't stay correct without anyone watching.