Stop 01 · DevOps FoundationsTopics · 1/9

What DevOps Actually Is

In short

Developers want to ship new features. Operations wants the servers to stay calm. For years they fought. DevOps is the way of working where both sides own the whole thing together.

DevOps is a set of practices and a culture that breaks down the wall between development and operations teams — automating and streamlining how software gets built, tested, released and run.

The mascot in a sweet shop passes a fresh tray of jalebis from the kitchen straight to the counter.

Think of it like this

The halwai and the counter staff

In a busy mithai shop, the halwai makes the sweets and the counter staff sells them. If the counter blames the kitchen for stale jalebis and the kitchen blames the counter, customers suffer. When they share one goal, happy customers, the shop runs smoothly.

Watch it happen

Before and after DevOps

Wall between teams

Devs throw code over the wall
Ops deploys by hand, rarely
Outage? Everyone blames someone else

DevOps way

One team owns build to run
Small releases, many times a week
Outage? Fix it, then fix the process

DevOps is not a tool or a job title first. It is shared ownership, backed by automation.

The big ideas

What you need to know

Culture before tools

Buying Jenkins or Kubernetes does not make a team DevOps. People sharing responsibility for production does.

Small changes, often

Ten tiny releases are safer than one giant one. If something breaks, you know exactly which change did it.

Automate the boring parts

Builds, tests and deployments run by script, not by someone clicking through a checklist at midnight.

Watch what happens live

Monitoring tells the team how real users experience the app, so problems are spotted before customers complain.

How it works

How one change travels in a DevOps team

1
Write
A developer makes a small change and pushes it to Git.
2
Check
An automated pipeline builds the code and runs the tests.
3
Ship
If everything passes, the change is deployed without a manual handover.
4
Watch
Dashboards and alerts show if the change hurt anything, and the same team responds.

Save yourself the pain

Common mistakes

Oops

Thinking DevOps means one person who does all the server work for everyone.

Do this instead

DevOps is a way the whole team works. A DevOps engineer helps build the automation, but devs still own their code in production.

Oops

Believing you are 'doing DevOps' because you installed a CI tool.

Do this instead

Tools help, but if releases still need a week of approvals and blame, nothing has changed. Measure how fast and safely you ship.

Your mission

Spot the wall

~15 min

Quick check

A company hires one 'DevOps engineer' but devs still hand code to ops monthly by email. What is missing?

Go deeper

1Read 2-3 'day in the life of a DevOps engineer' posts from different companies.
2List 3 friction points a company might face without DevOps practices (slow releases, manual deploys, firefighting).
3Notice DevOps is a culture and set of practices, not a single tool you install.