"Owner or not" is a false dichotomy. I get it that the author and many SREs are probably jaded from developers not taking ownership at all. The right attitude

"Owner or not" is a false dichotomy. I get it that the author and many SREs are probably jaded from developers not taking ownership at all. The right attitude is to figure out processes that let people draw a line when to go to DevOps, and when to escalate to developers. Developers need to understand the costs they impose on devops and organizations need to make sure developers are empowered to fix their own issues, rather than to be constantly chased around to business requirements. Developers ultimately answer to business priorities, and they don't necessarily own the business processes that demand their support. If developers are given ample resources to keep bugs out of systems, document operational expectstions and respond to incidents, then the developers can "own" the processes better. If not, it's a management problem that is just of the same nature as the usual SRE complaint that developers don't want to own anything at all.