Turns out most people really want to do a good job. Software ownership leads to better outcomes, and people crave autonomy and agency by default.
So if your team is against the idea, either you're fucking something up (messaging, incentives) or they have a lot of past trauma.
So if your team is against the idea, either you're fucking something up (messaging, incentives) or they have a lot of past trauma.
Honestly, these days I don't hear from many developers who don't want ownership. I hear more often that devs want it but ops won't let them have it.
Which tells me we haven't been including ops enough in our storytelling and sales pitch. 🤔
Which tells me we haven't been including ops enough in our storytelling and sales pitch. 🤔
I get it. For those of us who have been ops-ing for years, on call is an identity, a cultural lodestone, a shared trauma that defines who we are -- why we matter.
We are the watchers on the wall, the fire that burns against the cold, etc. It's powerful shit.
We are the watchers on the wall, the fire that burns against the cold, etc. It's powerful shit.
But the world changes, and myths have to change too. The old ops myth was heroism and sacrifice. The new myths are around ops as force amplifiers, caretaking of systems and teams; ops as specialized systems experts who can level up entire teams at production-readiness
