Is faster actually safer? How software physics beats human psychology
Is faster actually safer? How software physics beats human psychology

Is faster actually safer? How software physics beats human psychology

Sometimes doom-scrolling through Twitter has its rewards. A few weeks ago, in between the Ever Given🚢 memes (how we miss the big boat!) and the usual screams😱 into the void, I came across this from Charity Majors (@mipsytipsy), CTO at @honeycombio

That’s it. That’s the Tweet.

These are such great analogies. Unless we’re running away from imminent danger🦁, humans have a really hard time processing that faster is safer. Usually, when we feel threatened or uncertain, we slow down, take our time and look at our options. 🤔

Even in relatively comfortable situations we sense that increasing our speed will also increase our risk. And in the world of software these “deep seated biological impulses” create human barriers to automation.

Yeah, why is that?

There are several reasons why tech leads and managers cling to these deep seated notions of predictability, safety and routine. Continuous delivery scares them because…..

  • They don’t trust their teams to push desirable changes to PROD every 20 minutes ❌
  • They think batching changes means more oversight (also great for spreading any potential blame around 👍)
  • They think slower deploys 🐌 makes for higher quality and fewer bugs

DevOps people know none of this is true. Low frequency deploys and batched changes aren’t good for productivity, but they do give managers the illusion of control. And because the idea that “faster is safer” doesn’t feel right people will make all kinds of trade-offs to hold on to that illusion.

via GIPHY

Wizadora, nothing’s surer.

As ever, DORA❤️ has findings that back up what we see in the field. In the 2018 report they found that “misguided performers suffer from a cautious approach.” It’s worth quoting at length:

“We often hear from organizations that prefer to take a cautious approach to software development and delivery. They assure us—and their stakeholders—that releasing code infrequently can be an effective strategy as they use the extra time between deployments for testing and quality checks to minimize the likelihood of failure. For the most part, they achieve that goal.”

Notice the positive reinforcement. They believe slow is safe and they’re even seeing results that confirm those beliefs. It’s all fun and games until someone loses an eye though. The report continues:

“Developing software in increasingly complex systems is difficult and failure is inevitable. Making large-batch and infrequent changes introduces risk to the deployment process. When failures occur, it can be difficult to understand what caused the problem and then restore service. Worse, deployments can cause cascading failures throughout the system. Those failures take a remarkably long time to fully recover from.” 😬

How long exactly⏰? DORA found that anywhere between 1 and 6 months was a reasonable ball park for full recovery. And it was all going so well! We were on the ice and inching along. Suddenly, we’re flat on our faces with no easy way of getting back up. Turns out slow wasn’t that safe after all.

via GIPHY

Plus ca change!

We found something similar in a previous post on the FCA’s report on Implementing Technology Change.

Asked to grade their own homework ✅, managers thought that their costly and time-consuming change management processes were effective precisely because they were costly and time-consuming!

via GIPHY

If it costs money and takes time it must be doing something, right? Managers were buying into that illusion even as they reported that change failure rates were the single biggest cause of incidents. Cognitive dissonance to the moon! 🚀 🌝

Charity’s tweet inspired me (thank you🙏!) because the idea that “speed is safety” applies to change management as well as continuous delivery. They’re part of the same value stream. If you can automate🤖your change and release controls as part of your DevOps pipelines there’s no reason to delay release candidates because some guy👨🏻‍💼with a clipboard needs to eyeball 👀 them first.

Managers still see their job as a high wire act where a pinky toe either side of the rope means disaster. We need to encourage them to go faster by thinking more like ice skaters and less like tightrope walkers.

via GIPHY

Top Articles

DevOps Engineer in Customer Success and Developer Relations 🚀

DevOpsCon: Munich & Online. Making friends with change

What does it mean to deliver software with Continuous Compliance?

Published April 28, 2021 in
Bruce Johnston
Bruce Johnston

Subscribe to The Merkely Meteor for all the latest news, updates and ch-ch-changes

Subscribe to the Merkely Meteor

More posts in features

It’s time to say “Ok, Boomer!” to old school change management

For technology organizations, change is inevitable. From operational changes in the form of mergers and expansions to frequent software updates and bug fixes, change management is of utmost importance. But, it’s this second aspect of change, at the level of the code, that takes increasing precedence in today’s software driven organizations because it affects day-to-day tasks as well as high-level management.

The Jan Bosch Interview: The Future for Technology Companies

A few days ago you posted a video from the Software Center about doing continuous testing in regulated, safety critical environments. And it immediately attracted a bunch of objections from people in the comments.

10 outdated beliefs about software

The world of software remains a fascinating place and I keep being amazed at how rapidly it continues to evolve and transform. We certainly have come a long from the early 1980s when I was a teenager programming BASIC on my ZX81.

Subscribe to The Merkely Meteor for all the latest news, updates and ch-ch-changes

Merkely is committed to protecting and respecting your privacy. Don’t worry if you change your mind you can opt out at any time - Review our Terms and conditions and Privacy Policy
Subscribe
Merkely is committed to protecting and respecting your privacy. You can unsubscribe at any time by clicking the link in the footer of our emails. For information about our privacy practices, please visit our Privacy Policy.
Subscribe to the Merkely Meteor