Ep 1: What is DevOps?
In one sentence: DevOps is a way of working where the people who build software (Dev) and the people who run it (Ops) work as one team, with automation, so changes reach users quickly and safely.
The old way: “over the wall”
Section titled “The old way: “over the wall””For years, developers wrote code and then handed it over to an operations team to put on servers. Picture a wall between them:
- Dev wants to ship new features fast.
- Ops wants the system to stay stable, and every change is a risk.
Code was thrown “over the wall”. When something broke in production, Dev said “it worked on my machine” and Ops said “your code broke our servers”. Releases were slow, rare and scary.
The DevOps way: one team
Section titled “The DevOps way: one team”DevOps removes the wall. The same team plans, builds, tests, releases and watches the software. They use automation (tests, pipelines, scripts) so that shipping a change is routine instead of an event.
| Old way | DevOps way |
|---|---|
| Big releases a few times a year | Small changes, often |
| Manual steps, checklists | Automated pipelines |
| “Not my problem” | Shared ownership |
| Finding out from angry users | Monitoring and fast feedback |
Key terms
Section titled “Key terms”- Dev (development): writing and changing the code.
- Ops (operations): running the code on servers so users can use it.
- Production: the live system real users use.