The shift from a culture of siloed Dev and Ops teams to a more integrated approach indeed accelerated with the rise of cloud services and new tooling. It's also intriguing to see how the term "DevOps" has taken on a life of its own, spawning various offshoots like DevSecOps, FinOps, and GitOps.

However, I'd like to propose a slightly different perspective on the "death of Ops." Yes, traditional system administration tasks have largely been abstracted by the cloud and other technologies. But we could argue that Ops has evolved rather than become obsolete. Ops tasks have become more complex and varied, dealing with cloud infrastructure, orchestrations, security, and more. The Ops in DevOps may no longer involve managing on-premise servers, but it's now about managing and optimizing a whole new set of tools and services in the cloud ecosystem.

Moreover, the concept of "NoOps" may seem appealing on the surface, but it's not always viable or even desirable. The need for deep system knowledge, troubleshooting skills, and the ability to optimize for cost and performance—these are areas where Ops professionals still add significant value.

In essence, DevOps has indeed catalyzed a shift in culture and practice in software engineering, but it doesn't signal the end of Ops. Instead, it marks a transformation of what Ops means in our modern, cloud-centric world.