[itsdanweston]

There are two main things I do. The first is to make sure everything runs as expected, with no faults, no security risks, deployments are successful, etc.

The second (and personally more important) thing I do is try to remove as much friction from the dev's experience as possible. I go and chat with the devs, find out what parts annoy them, where they get stuck, and what level of control they want to have. Then I go away and try and resolve those issues.

For me, DevOps is more about Dev than Ops. I started as a dev, and nothing kills productivity for me more than waiting for the pipeline, not being able to find where logs are being sent, not being able to get access to the Kube cluster and so on. So I do what I can to make the devs happy, happy devs generally equals better outcomes.