> never target automation of 100% of incoming workload... Iteratively approach it. This is critical. So many people jump from "it works" to "let's automate it

> never target automation of 100% of incoming workload... Iteratively approach it. This is critical. So many people jump from "it works" to "let's automate it entirely" without understanding all the nuances, all the various conditions and intermediate states that exist in the real world. The result is a brittle system that is unreliable and requires constant manual intervention. A better approach is to semi-automate things first. Write scripts with manual QA checkpoints and playbooks that get executed directly by devs. Do the thing yourself until it's so boring it hurts. Then automate it.