DevOps
A cultural philosophy that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle.
A cultural philosophy that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle.
## Breaking Down Silos **DevOps** is not a job title (though "DevOps Engineer" exists); it is a cultural shift. Traditionally, Developers wrote code and "threw it over the wall" to Operations to run. When it broke, Ops blamed Dev, and Dev blamed Ops. DevOps destroys that wall. **"You build it, you run it."** ### The Three Ways of DevOps (The Phoenix Project) 1. **Flow**: Optimize the flow of work from Development to Operations (CI/CD). 2. **Feedback**: Amplify feedback loops from Ops back to Dev (Monitoring, Paging). 3. **Continuous Learning**: Experiment, fail fast, and improve daily. ### DevOps vs. Agile * **Agile** optimizes the development process (Ideas -> Code). * **DevOps** optimizes the delivery process (Code -> Production).
ExThe Friday Deploy
"A company had a rule: "No deploys on Friday" because manual deploys were risky."
Why DevOps Matters
DevOps kills the "throw it over the wall" mentality.
Enables high-velocity delivery without sacrificing stability.
Lets developers own their code in production.