It's really about day to day decisions being "pipeline driven" - allowing automated pipelines to make continuous tactical decisions that humans usually make in "traditional" processes. When to merge, is it secure?, when to deploy, is it up? when to spin up an environment? when to rollback, when to enable a flag, when to declare "all OK" etc.

This also means, not just dev and ops skills. It's also testing, also security, also compliance. "pipeline driven" is what we are after. And this of course enables true continuous delivery.

"DevOps" is another Silo. Which is why we also have "DevSecOps" and "TesOps" etc...

I'm in the process of writing a new book about this new-old idea: https://leanpub.com/pipelinedriven/