DevOps Engineer Track
5 series · 60 parts · ~40 hours
This is the DevOps path I wish someone had handed me when I started. No certification upsell, no skipped fundamentals — just the sequence that actually works: Linux first, then containers, then orchestration, then the roadmap that ties it together, and finally AWS where it all runs in production.
Every part below is written from systems I personally run. When a tutorial says "this breaks at 2 AM," it's because it broke for me at 2 AM. Work through the modules in order — each one assumes the previous.
Linux Fundamentals
Everything starts here. Permissions, processes, networking, shell — the layer every other tool sits on.
Docker Containers
Package once, run anywhere. Images, volumes, networking, compose — from first container to production patterns.
Kubernetes
Container orchestration from zero: pods, deployments, services, scaling, self-healing — explained without jargon.
- Kubernetes Tutorial Part 1
- Kubernetes Tutorial Part 2
- Kubernetes Tutorial Part 3
- Kubernetes Tutorial Part 4
- Kubernetes Tutorial Part 5
- Kubernetes Tutorial Part 6
- Kubernetes Tutorial Part 7
- Kubernetes Tutorial Part 8
- Kubernetes Tutorial Part 9
- Kubernetes Tutorial Part 10
- Kubernetes Tutorial Part 11
- Kubernetes Tutorial Part 12
DevOps Roadmap
The big picture: CI/CD, IaC, monitoring, culture. How all the tools connect into a career.
AWS + Linux Combo
Where it runs for real. EC2, networking, storage and Linux administration on actual cloud infrastructure.
- AWS + Linux Combo Part 1
- AWS + Linux Combo Part 2
- AWS + Linux Combo Part 3
- AWS + Linux Combo Part 4
- AWS + Linux Combo Part 5
- AWS + Linux Combo Part 6
- AWS + Linux Combo Part 7
- AWS + Linux Combo Part 8
- AWS + Linux Combo Part 9
- AWS + Linux Combo Part 10
- AWS + Linux Combo Part 11
- AWS + Linux Combo Part 12
Essays & guides in this track
Frequently asked questions
Do I need a degree to become a DevOps engineer?
No. I transitioned into cloud engineering from running a business. What matters is demonstrable skill — systems you can show, problems you can debug, and fundamentals you actually understand.
How long does this track take?
Roughly 40 hours of focused reading, but real learning happens when you build alongside it. Budget 2–3 months if you practice each module on a real machine.
Should I learn Docker before Kubernetes?
Yes, always. Kubernetes orchestrates containers — if you don't understand what a container is, K8s concepts won't stick. That's why Docker is module 2 and Kubernetes is module 3 here.