Current program

DevOps Engineer Mastery

120 days · about 4 months11 phases3 available117 planned

A structured path from Linux and Git through cloud, CI/CD, containers, Kubernetes, and production engineering.

The spine

11 phases · 120 days

You are in one phase at a time. Gold is complete. Outlined gold is a published day. Quiet marks are planned titles, not empty pages.

Complete Now Available Planned

Phase 01Foundations
Days 1–120/12you are here
Phase 02Azure networking + identity
Days 13–180/6
Phase 03Write CI
Days 19–260/8
Phase 04First Terraform
Days 27–280/2
Phase 05Containers + app
Days 29–360/8
Phase 06Kubernetes
Days 37–620/26
Phase 07AKS
Days 63–760/14
Phase 08Terraform + Helm
Days 77–880/12
Phase 09Operate
Days 89–960/8
Phase 10Design + resume
Days 97–1080/12
Phase 11War room
Days 109–1200/12

Practice, not playback

How a day works

This is not a watch-and-copy course. Read the day, try it yourself, break one thing safely, debug what you see, then practise the questions. I will share exercises and interview questions. You still have to do the work.

01
Read
Understand the words. Predict what should happen before you run anything.
02
Try
Do the core task. On write days, your first version is yours — not AI's.
03
Break
Break one thing safely. Write down what you actually saw.
04
Debug
Logs, exit codes, and evidence. Chat is not a substitute for looking.
05
Practise
Answer the questions out loud. What fails, and how do you troubleshoot it?
06
Review
Check whether you can explain it. If you cannot, you do not own it yet.

Generated output still needs an engineer

Why DevOps before AI

AI can generate

Code
YAML
Scripts
Commands
Configs

You still need to

Understand
Review
Debug
Test
Secure
Deploy
Operate

AI can generate the files. You still have to understand them, catch what is wrong, run them, and live with the failure.

Later stages stay off the site until they are real

After this program

DevOps is the current program. Later stages stay off this site until there is real material.

Willing to practise

If you want to learn with me

If you are willing to put in the hours, you can learn along with me. I may help with doubts and debugging when the question shows real work.

Instagram and Telegram

Around the work

Daily posts go on Instagram. Discussion happens on Telegram. The 120-day plan stays here.

Shell, PATH, exit codes

Start at Day 1

Designed to help you build the skills and practical foundation needed to start attempting DevOps roles.

Open Day 1 Explore the 120-day plan

DevOps Engineer Mastery

120 days · about 4 months11 phases3 available117 planned

A structured path from Linux and Git through cloud, CI/CD, containers, Kubernetes, and production engineering.

11 phases · 120 days

You are in one phase at a time. Gold is complete. Outlined gold is a published day. Quiet marks are planned titles, not empty pages.

Complete Now Available Planned

Phase 01Foundations
Days 1–120/12you are here
Phase 02Azure networking + identity
Days 13–180/6
Phase 03Write CI
Days 19–260/8
Phase 04First Terraform
Days 27–280/2
Phase 05Containers + app
Days 29–360/8
Phase 06Kubernetes
Days 37–620/26
Phase 07AKS
Days 63–760/14
Phase 08Terraform + Helm
Days 77–880/12
Phase 09Operate
Days 89–960/8
Phase 10Design + resume
Days 97–1080/12
Phase 11War room
Days 109–1200/12

How a day works

Read

Understand the words. Predict what should happen before you run anything.

Try

Do the core task. On write days, your first version is yours — not AI's.

Break

Break one thing safely. Write down what you actually saw.

Debug

Logs, exit codes, and evidence. Chat is not a substitute for looking.

Practise

Answer the questions out loud. What fails, and how do you troubleshoot it?

Review

Check whether you can explain it. If you cannot, you do not own it yet.