DevOps for Beginners
by Sergey Okinchuk
IntroTwo Different Jobs: Building vs Running

Chapter One · Part 1: Why DevOps Exists

The Problem DevOps Solves

Before any tool, any pipeline, or any of the words you came here to learn, there is a problem — a simple, human one about who builds software and who keeps it running. This chapter is that problem, and the idea invented to fix it. Everything else in the course follows from here.

4 topics

It is tempting to think DevOps starts with tools — Git, Docker, a pipeline. It doesn't. It starts with two jobs that pull against each other: writing new software, and keeping the running software stable. For years those jobs lived on separate teams with a wall between them, and that wall is exactly what DevOps tears down.

Four short topics build the picture. First, the two different jobs and why they naturally conflict. Then the wall that grew between the teams that did each, and the blame and slow, scary releases it caused. Then what DevOps actually is — a way of working, not a tool you buy. And finally the feedback loop at its heart: ship small, watch, learn, repeat.

One goal, split into two jobs that pull in different directions
Development
Maya's side — writing and changing the code, adding features. Rewarded for change.
Operations
Sam's side — deploying it and keeping it online for real users. Rewarded for stability.
DevOps
The two jobs done by one team that shares the work and the responsibility — build it and run it.

Topics in This Chapter

Topic 01
Two Different Jobs: Building vs Running
Meet Maya and Sam — the developer who builds Pageturn and the operator who keeps it online — and the tension built into their two jobs that the rest of the course exists to ease.
Concept
Topic 02
The Wall Between Dev and Ops
How code used to be "thrown over the wall" from one team to the other, the blame loop that followed, and why releases became rare, big, all-at-once events everyone dreaded.
Concept
Topic 03
What DevOps Actually Is
Not a tool, not a job title — a way of working where the people who build software and the people who run it act as one team. The idea the famous infinity loop draws out.
Concept
Topic 04
The Feedback Loop
The engine inside DevOps: ship a small change, watch what happens, learn, and let that shape the next one. Why small and frequent beats big and rare every time.
Concept