> "Did you really want to transfer from development to ops?" which me think that a lot of developers look down on operations roles and see it as a demotion.
I would certainly see it as a departure from what I want to do - design, build and deliver systems. I'm not really in it for the continuity operations.
Then, and I don't know of a nice way to say this, the systems you design, build, and deliver are going to be unreliable and flawed.
Owning (as in caring about and as in business responsibility) the reliability and operation of systems you build, at least for a while after they stabilize, is critical if you want to produce quality products. After all, operational flakiness is a UX issue.
> Then, and I don't know of a nice way to say this, the systems you design, build, and deliver are going to be unreliable and flawed.
Sorry but that's utter bollocks. I'm not interested in being in ops, therefore my software is shit?
> Owning (as in caring about and as in business responsibility) the reliability and operation of systems you build ... is critical.
But that's not being in ops. That's about taking an interest in the running system.
You've just jumped on me saying I'm not interested in having a role in ops because I like to build software, and run off to some weird unsupported conclusion that I just write code and abandon it. I don't need to have a business responsibility for the running system in order to support it and be responsive to the ongoing needs of those that do.
I would certainly see it as a departure from what I want to do - design, build and deliver systems. I'm not really in it for the continuity operations.