DevOps
/dɛvˈɒps/ · Noun · Development · Origin: 2009
Definitions
DevOps is a cultural and technical movement that unifies software development (Dev) and IT operations (Ops), emphasizing collaboration, automation, and continuous improvement across the entire software delivery lifecycle. Rather than treating development and operations as separate silos with conflicting goals, DevOps encourages shared responsibility for building, deploying, and maintaining software. Key practices include continuous integration and continuous deployment (CI/CD), infrastructure as code, automated testing, monitoring and observability, and incident response. DevOps teams use tools like Git, Jenkins, Docker, Kubernetes, Terraform, Ansible, Prometheus, and Grafana to automate repetitive tasks and create reliable, repeatable processes. The goals are faster delivery of features, more stable operating environments, shorter feedback loops, and improved mean time to recovery (MTTR) when incidents occur. DevOps is often complemented by related movements like Site Reliability Engineering (SRE) and Platform Engineering. Adopting DevOps is as much about changing organizational culture and breaking down team boundaries as it is about adopting specific tools.
In plain English: The idea that developers and the people who run servers should work closely together instead of throwing code over a wall — with lots of automation in between.
The Three Ways of DevOps (from 'The Phoenix Project'): systems thinking (optimize the whole, not parts), amplifying feedback loops (shorten and amplify feedback from production), and continuous experimentation and learning. DevOps is a philosophy; the tools are just enablers.
Example: 'Buying Kubernetes doesn't make you DevOps any more than buying a gym membership makes you fit. DevOps is about culture, feedback loops, and shared ownership.'
Source: philosophy / Three Ways
Origin Story
A Belgian conference that ended the war between developers and operations
The term **DevOps** was coined by **Patrick Debois**, a Belgian IT consultant, in 2009. Frustrated by the wall between development teams (who wanted to ship fast) and operations teams (who wanted stability), Debois organized a conference in Ghent, Belgium, called **DevOpsDays**. The hashtag `#devops` took off on Twitter, and a movement was born.
The ideas behind DevOps predated the name. Andrew Shafer and Patrick Debois had discussed "Agile Infrastructure" at the Agile 2008 conference. John Allspaw and Paul Hammond gave their influential "10+ Deploys Per Day" talk at Velocity 2009, showing how Flickr blurred the dev/ops boundary. DevOps gave a name to practices that pioneering teams were already adopting.
DevOps isn't a tool or a job title (despite "DevOps engineer" becoming ubiquitous). It's a cultural philosophy: shared ownership of the entire software lifecycle, from writing code to running it in production. The practices it champions — CI/CD, infrastructure as code, monitoring, blameless postmortems — have become industry standard.
Coined by: Patrick Debois
Context: DevOpsDays, Ghent, Belgium, 2009
Fun fact: Patrick Debois chose the name 'DevOpsDays' partly because he wanted a name that fit in a tweet (Twitter had a 140-character limit at the time). The community shortened it to DevOps, and Debois has jokingly said he should have called it 'DevOpsDays' to keep the full name.