ScaryOps: The opposite of DevOps

TL;DR If you aren’t confident in your code you’re not doing DevOps you’re doing ScaryOps.

I really wish I had come up with this term but I didn’t. Thanks Jude Clermont for coining it.

We were discussing automation of deployment of Azure resources and I said “Let’s delete everything and start again”. Jude looked a little startled.

“It’s okay”, I commented as I thought it through, “we have the code so we can just rebuild it the old way if the new way doesn’t work”.

“If we can’t rebuild it then we’re doing ScaryOps not DevOps.” Jude’s response hit me like a gin-soaked lemon to the forehead.

If you cannot destroy all of your configuration and rebuild it, we’ll talk about conservation of content in a later post, then you aren’t doing DevOps because that means you have to hand hold every deployment. Your pet sitting again, not cattle farming.

So Simple Innovations has a new catch phrase:

We do DevOps not ScaryOps.

Thank you Jude.

TL;DR If you aren’t confident in your code you’re not doing DevOps you’re doing ScaryOps.