Skip to main content
Question
Anonymous
Asked a question last month

How can DevOps save time?

What are you looking for lately?

From: https://medium.com/@hello_44104/3-ways-devops-saves-time-96dd814afff97

It lists ‘three ways DevOps efforts help save time’:

1. ENABLING THE DEVELOPER

2. SHIFTING LEFT? WHAT’S RIGHT?

3. LEARNING TO HANDLE FAILURE

This is a really interesting list that I wouldn't have made myself but I totally agree with. 

1. ENABLING THE DEVELOPER

We save time when work flows. Cutting handoffs, delays, and friction all help. Empowering individuals to make decisions, access tools, and leverage capabilities also goes a long way.

2. SHIFTING LEFT? WHAT’S RIGHT?

Starting sooner and running activities in parallel save us time in the long run. Shifting left moves action upstream, so we're not leaving what needs to be done until there's nothing left to do otherwise. 

3. LEARNING TO HANDLE FAILURE

To me this is shifting tactics left and designing for failure. If we can anticipate issues (which we usually can), then we can build mitigation into the system and react quickly. Driving down MTTR (Mean time to recovery) is all about having automated or easy fixes available for anticipated issues.