Member-only story

The DevOps Paradox: A Shift Away from Ops

A short story about DevOps evolution — DevOps meant Dev and Ops collaboration, but they removed Ops from the equation instead

Alexandre Couëdelo
Better Programming
5 min readMay 18, 2023
Photo by Fotis Fotopoulos on Unsplash

These days, we have such a hard time defining DevOps because the problem it initially solves is long gone.

For some recent companies, the problem never actually existed! They are doing everything correctly, but instead, the software engineering landscape has evolved so fast that the gap has been filled by tooling and cloud engineering.

We are far from the original day of DevOps and its culture shift aiming to break the silos between Dev and Ops.

The Dev and Ops Silos

Back in 2008, when Patrick Dubois first thought about DevOps, he was looking at the ineffective collaboration between development and operations in a context where project management had just moved from waterfall to Agile.

The operation teams at that time managed everything from networking, server, virtual machine, OS, and software updates. This effectively hid a lot of manual operations. Not everything was manual, but it was before Puppet, Chef, and Ansible — or even Terraform existed.

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Alexandre Couëdelo
Alexandre Couëdelo

Written by Alexandre Couëdelo

Software Supply Chain and Automation Specialist (aka. DevOps).

Responses (6)

What are your thoughts?