You are not reading or understanding comments, child. That's not what I said whatsoever.

You're of the opinion that DevOps engineers can be automated away. I proved you wrong. Now you're talking about the tooling, which is in my first comment to you. Automated tooling is NOT all DevOps is, and the fact you think shows me you're unseasoned in whatever it is you do, have no concept of the role.

It would be people like you who would not pass the first round of interviews from answering a question about this topic exactly as you've stated, because you don't understand the core function of the team, and you're role in it.

You make some code, and obviously have no idea how to run it, let alone at scale. All the working pieces of a platform at large need to be understood and vetted by a DevOps team in order to make it run, and run well. That's understanding everything from start to finish, in ways you wouldn't be able to comprehend being one part of team that is building one part of a platform. You can't make an agent that understands all the underpinnings of all the services or metrics, and why they fail, that then takes action on them, because it's not something AI does. Case in point, the AWS outage and others I mentioned.

Now, you could make MANY agents that take actions on many things, but that doesn't give situational awareness or comprehension to any singular agent, something AI also doesn't do. That's what DevOps teams do.

I don't even need to keep arguing with you about this, because the down votes on your comments speak for themselves. I'm just trying to educate on your false understanding about how it all works so you don't stumble through your career making the same comments and mistakes.