4 ms·

Ehh, at least in todays world where teams that focus on operations in a DevOps environment, there are a lot more metrics that operations teams can be measured b

by zjaffee 10y ago

Ehh, at least in todays world where teams that focus on operations in a DevOps environment, there are a lot more metrics that operations teams can be measured by other than just uptime. For example, lets say a decision is made that you want to spin up a new environment, deploy a new service, scale up or scale down a piece of infrastructure. A good operations team in this more modern space will have automated the vast majority of the work needed to do such things, and in turn, vastly improve developer productivity since they do not need to wait a month on operations to do such work.

hibikir 10y ago
But how do we know what good automation is? It's easy to see terrible ops work, but it's hard to see amazing ops work. This leads many organizations to end up thinking that ops skill is about outage response. Guess what: The person that is best at fixing at outage is typically the one that caused it! Imagine I have two people in an ops team: One writes a lot of new code, and ships a lot of buggy features, and quickly reacts to the problems. People get the impression that they are working on something hard, and they are grateful for all the hard work. Another one takes longer to ship, but the automation just works. Therefore, whatever he was doing was easy, and they are just slow at doing it. So sadly, in most environments it pays off to actually have problems in your ops automation, for the visibility that you get by saving the day.
gaius 10y ago
"It's easy - I just click a button! What the hell are we paying all these guys/gals for?"
- asimuvPR 10y ago
  I always compare this with a mailbox and people get it. When you deposit a letter it just doesn't arrive magically to its destination. People, cars, trucks, trains, boats, and planes are part of the process tve gets your letter delivered. Their eyes usually open wide once understood.

by zjaffee 10y ago

hibikir 10y ago

But how do we know what good automation is? It's easy to see terrible ops work, but it's hard to see amazing ops work. This leads many organizations to end up thinking that ops skill is about outage response. Guess what: The person that is best at fixing at outage is typically the one that caused it! Imagine I have two people in an ops team: One writes a lot of new code, and ships a lot of buggy features, and quickly reacts to the problems. People get the impression that they are working on something hard, and they are grateful for all the hard work. Another one takes longer to ship, but the automation just works. Therefore, whatever he was doing was easy, and they are just slow at doing it. So sadly, in most environments it pays off to actually have problems in your ops automation, for the visibility that you get by saving the day.

gaius 10y ago

"It's easy - I just click a button! What the hell are we paying all these guys/gals for?"

asimuvPR 10y ago
I always compare this with a mailbox and people get it. When you deposit a letter it just doesn't arrive magically to its destination. People, cars, trucks, trains, boats, and planes are part of the process tve gets your letter delivered. Their eyes usually open wide once understood.