What DevOps Actually Is
Here is the definition the rest of the course rests on. DevOps is a way of working in which the people who build software and the people who run it act as one team, sharing the work and the responsibility from idea all the way to live and back again. That's it. It's a culture and a set of practices — not a product, not a department, not a title.
That last point catches almost everyone, so let's be blunt about it. You cannot buy DevOps, install DevOps, or hire a DevOps to sit in the corner. The famous infinity-loop symbol you'll see on slides isn't a tool either — it's just this idea drawn as a never-ending cycle of build and run, with no wall in the middle.
Not a Tool, Not a Title
It's worth saying plainly what DevOps is not, because the word gets stuck onto so many things. It is not a single piece of software like Git or Docker — those are tools that help you work this way, but owning them is not "doing DevOps." It is not simply a new name for the old operations job. And it is not a box on the org chart you can fill by hiring one person.
DevOps is the culture and the habits: how a team decides to share ownership, release often, and learn from what happens in production. The tools exist to make those habits practical at scale — which is why the rest of this course spends its time on them — but the habits come first.
One Team, End to End
The core move is to erase the wall from the last topic. Instead of one team building and a different team running, the same team does both. The principle has a slogan you'll hear constantly: "you build it, you run it." If Maya's team ships a Pageturn feature, Maya's team is also on the hook for keeping it healthy in production.
This sounds like more work for developers, and in a way it is. But it changes everything, because now the person who can fix a problem is the same person who feels it. When you know you'll be the one woken up if your code misbehaves at 2am, you write it — and watch it — very differently.
Practices and Automation Together
If the culture sets the goal, automation is what makes the goal reachable. A single team can only build and run and watch all of Pageturn if the repetitive parts — testing every change, packaging it, deploying it, keeping an eye on it — happen automatically rather than by hand. Culture decides to release often; automation makes releasing often actually survivable.
So the two always travel together. Tools without the culture just automate the old, walled-off way of working. The culture without tools collapses under the manual effort. DevOps is the pair: a way of working, and the automation that lets a team live it.
- "DevOps is a tool — the pipeline, or some app." Tools support it, but DevOps itself is the way of working. Buying the tools is not the same as adopting the culture.
- "DevOps is just a fancier name for the operations team." It's the opposite of keeping them separate — it merges building and running into one shared responsibility.
- "A company can finish adopting DevOps and be done." It's an ongoing way of working, like a team's habits, not a project with a finish line.
- "'You build it, you run it' means there's no operations work." The operations work still exists — it's just owned by the people who built the thing, not handed off to strangers.
- This is the definition the whole course builds on — every later tool is a way to make this way of working practical.
- It saves you from the most common misunderstanding in the field: treating DevOps as software you install rather than a way a team works.
- "You build it, you run it" explains why later chapters on monitoring and on-call land on the same team that writes the code.
- Knowing culture comes first helps you read job posts and team claims critically — owning a pipeline isn't the same as working this way.
Knowledge Check
Which best describes what DevOps actually is?
- A way of working where building and running software are one shared responsibility
- A specific piece of software you install to manage servers
- A new name for the traditional operations team and its work
- A single job title for the one engineer who personally handles all of the deployments
What does the slogan "you build it, you run it" mean?
- The team that builds the software is also responsible for running it in production
- Operations work no longer needs to happen at all
- Every developer must work completely alone with no teammates
- Users themselves are expected to run and maintain the software entirely on their own
Why do the culture and the automation always go together in DevOps?
- The culture sets the goal; automation makes reaching it practical at scale
- Buying enough of the right tools automatically creates the culture on its own
- The culture works perfectly fine with no automation behind it
- They are unrelated and just happen to share the same name
You got correct