DevOps is a set of practices and a cultural philosophy that aims to shorten the feedback loop between writing code and running it in production by breaking down the traditional separation between development and operations teams. The name is a portmanteau of development and operations.

Historically, developers wrote code and handed it over a wall to an operations team who ran, deployed, and maintained it. The two teams had different incentives: developers wanted to ship new things; operations wanted stability. This tension produced slow, infrequent releases and a lot of blame-shifting when things broke.

DevOps addresses this by making developers responsible for the full lifecycle of their software: building, testing, deploying, monitoring, and operating it in production. “You build it, you run it,” as Werner Vogels (Amazon CTO) put it.

The technical enablers of DevOps are largely CI/CD pipelines, infrastructure as code, and observability tooling. Infrastructure as code means servers, networks, and environments are defined in version-controlled configuration files (Terraform, Ansible, Kubernetes manifests) rather than set up manually. This makes environments reproducible and changes auditable.

Observability is the other pillar: if developers are responsible for production, they need to be able to see what is happening in production. This means structured logs, metrics dashboards, and distributed tracing so that a broken deployment is visible within seconds rather than discovered by users.

The cultural shift matters as much as the tooling. A team that has CI/CD and monitoring but still treats operations as “someone else's problem” does not get the benefits. DevOps works when the team that writes the code has enough ownership and access to deploy and diagnose it.