🎮 The Doer's Path — proof, not vibes¶

Core truth: Confidence content se nahi aati. Confidence verified reps se aati hai. Ye page handbook ko padhne ki cheez se khelne ki cheez banata hai: har lab ka proof-of-work check, ek badge ladder, aur ek streak system. Tick tumhara opinion hai; ✅ script ka verdict hai. Script jhooth nahi bolti.

The Loop (yahi poora system hai)¶

flowchart LR
    READ["📖 READ<br/>20% time<br/>module ka concept"]:::read
    DO["🔨 DO<br/>60% time<br/>lab, apne haath se"]:::do
    PROVE["🧪 PROVE<br/>check script chalao<br/>✅ ya ❌ — machine decides"]:::prove
    FIX["🔧 FIX<br/>hint padho,<br/>wapas DO pe"]:::fix
    BADGE["🏅 proof line<br/>progress.md me paste<br/>+ streak +1"]:::badge

    READ --> DO --> PROVE
    PROVE -->|"❌ fail"| FIX --> DO
    PROVE -->|"✅ pass"| BADGE -->|"agla module"| READ

    classDef read fill:#e3f2fd,stroke:#1976d2,color:#0d47a1;
    classDef do fill:#e0f2f1,stroke:#00897b,color:#004d40;
    classDef prove fill:#f3e5f5,stroke:#8e24aa,color:#4a148c;
    classDef fix fill:#fff8e1,stroke:#f9a825,color:#7a5c00;
    classDef badge fill:#e8f5e9,stroke:#43a047,color:#1b5e20;

Fail hona feature hai, bug nahi — fix→re-run loop hi asli seekhna hai. Production me yahi loop roz chalta hai; yahan bas stakes zero hain.

The only rule that matters

Module tab tak DONE nahi jab tak uska check script ✅ PASS na bole. Padh liya + samajh aa gaya + "kar lunga" = NOT done. Ye rule tumhe us jaal se bachata hai jisme har self-learner girta hai: reading that feels like doing.

🧪 Proof-of-Work checks — kaise chalayein¶

Scripts handbook repo ke labs/ folder me hain. Ek baar clone karo, phir har module ke baad:

git clone https://github.com/grvtech1/devops-handbook.git && cd devops-handbook
bash labs/check-m4-k8s.sh        # example — M4 ke baad

Har script:

✅ evidence check karta hai, yaadaasht nahi — kya cluster me sach me tumhara Deployment hai? kya git history me sach me revert commit hai?
❌ har fail ke saath exact fix hint deta hai — Google nahi, hint follow karo
🔥 kuch checks live drill karte hain — M4 wala script tumhara pod khud delete karke dekhta hai ki self-heal hota hai ya nahi
🏆 pass hone par ek PROOF LINE deta hai (✅ m4-k8s · 2026-07-25) — usse My Progress ki Labs Verified table me paste karo

#	Check script	Verify karta hai	Module
0	`check-m0-linux.sh`	Linux env · redirection (`>`) · chmod +x · chmod 644 · awk field extract · ss port snapshot	Linux Toolkit
1	`check-m1-terraform.sh`	`terraform validate` · non-empty state · plan = no changes (idempotency)	M1
2	`check-m2-ansible.sh`	ping→pong · playbook clean run · handler pattern	M2
3	`check-m3-docker.sh`	daemon · self-built image · layer inspection	M3
4	`check-m4-k8s.sh`	Deployment+Service+ConfigMap · LIVE self-heal test	M4
5	`check-m6-cicd.sh`	Actions workflow · docker build · SHA-tag (not :latest) · scan gate	M6
6	`check-m7-gitops.sh`	ArgoCD pods · app Synced+Healthy · self-heal ON	M7
7	`check-m7-incident.sh`	bad commit + revert commit in git · cluster clean — war story verified	M7 Lab 6
8	`check-m75-helm-kustomize.sh`	live release · revision>1 (rollback done) · overlay renders	M7.5
9	`check-m8-observability.sh`	monitoring stack · ServiceMonitor · `kubectl top` · HPA	M8
10	`check-capstone1-shortener.sh`	namespace · Deployment ready · Service endpoints · Secret · ArgoCD Synced+Healthy · LIVE /health + round-trip /shorten→redirect	Capstone I
11	`check-capstone2-microshop.sh`	all 3 Deployments ready · Redis up · 4 Services with endpoints · Ingress exists · ArgoCD Synced · INTER-SERVICE DNS verified (order-api → catalog-api by name)	Capstone II

Capstone checks chalane ka tarika:

# Capstone I — URL Shortener complete hone ke baad:
bash labs/check-capstone1-shortener.sh          # default namespace
bash labs/check-capstone1-shortener.sh <ns>     # custom namespace

# Capstone II — MicroShop complete hone ke baad:
bash labs/check-capstone2-microshop.sh          # default namespace
bash labs/check-capstone2-microshop.sh <ns>     # custom namespace

Pass hone par ye PROOF LINES milti hain — inhe progress.md me paste karo:

✅ capstone1-shortener · YYYY-MM-DD    ← 🚀 SHIPPER badge unlock
✅ capstone2-microshop · YYYY-MM-DD    ← 💪 BATTLE-TESTED badge unlock

🇮🇳 Hinglish intuition: Gym me mirror-selfie ≠ progress; weight ka number progress hai. Check script = weight ka number. Jhooth nahi bolta, ego nahi sunta.

⚡ Level 2 — CI-verified proof (GitHub-native)¶

Local check bash labs/... tumhare apne machine pe chalta — bharosa tum pe hai. Ise ek level upar le jao: apna lab-kaam ek GitHub repo me push karo, jahan ek CI pipeline usse verify kare — bilkul jaise asli job me PR pe hota hai. Pass hua to hub me us module pe ⚡ CI-verified badge jal jaata hai — jise koi fake nahi kar sakta (real Git history + green pipeline).

Yahi platform ka asli superpower hai: tum sirf CI/CD padhte nahi — tumhara apna seekhna khud ek CI pipeline pe chalta hai.

Kaise:

labs/proof-repo/ template ko ek naya public repo (devops-handbook-labs) me copy karo.
Apne lab artifacts commit karo — terraform/ me .tf, docker/ me Dockerfile, k8s/ me manifests, kustomize/ me overlays, helm/ me chart.
Push karte hi Verify Labs pipeline chalti hai: terraform validate, hadolint, kubeconform, kustomize build, helm lint — har ek real gate.
Hub me 🔗 Connect proof repo pe apna GitHub username daalo → hub tumhari pipeline ka result padh ke ⚡ badge laga deta hai.

Ek check tabhi red hota jab file exist kare par galat ho — matlab green ka matlab genuinely "banta hai". Ye woh Git history hai jo interviewer ko dikha sakte ho.

🏅 Badge ladder — the journey map¶

flowchart LR
    START(["🎒 Day 0<br/>setup done"]):::lvl0
    B1["🔨 FIRST BLOOD<br/>koi 1 check PASS"]:::lvl1
    B2["🏗️ TOOLCHAIN<br/>checks 1-2-3 PASS<br/>(Ansible·Docker·K8s)"]:::lvl2
    B3["🔁 GITOPS OPERATOR<br/>checks 4-5-6 PASS<br/>(incl. incident drill)"]:::lvl3
    B4["👁️ ALL-SEEING<br/>check 7 PASS<br/>(observability)"]:::lvl4
    B5["🚀 SHIPPER<br/>Capstone I live<br/>git push → prod"]:::lvl5
    B6["💪 BATTLE-TESTED<br/>Gauntlet + Chaos<br/>5+ war stories"]:::lvl6
    FINAL(["🎯 JOB-READY<br/>interview bank +<br/>portfolio repos"]):::final

    START --> B1 --> B2 --> B3 --> B4 --> B5 --> B6 --> FINAL

    classDef lvl0 fill:#eceff1,stroke:#607d8b,color:#263238;
    classDef lvl1 fill:#e3f2fd,stroke:#1976d2,color:#0d47a1;
    classDef lvl2 fill:#e0f2f1,stroke:#00897b,color:#004d40;
    classDef lvl3 fill:#f3e5f5,stroke:#8e24aa,color:#4a148c;
    classDef lvl4 fill:#f1f8e9,stroke:#689f38,color:#33691e;
    classDef lvl5 fill:#fff8e1,stroke:#f9a825,color:#7a5c00;
    classDef lvl6 fill:#fdeeee,stroke:#d64545,color:#b23030;
    classDef final fill:#e8f5e9,stroke:#43a047,color:#1b5e20;

Har badge ka criteria script-verifiable hai — mood nahi. Badge claim karne ke liye progress.md me proof lines paste hone chahiye. Simple.

Badge	Unlock hota hai	Interview me iska matlab
🔨 First Blood	pehla ✅ PASS	"maine tools chalaye hain"
🏗️ Toolchain	m2+m3+m4 PASS	"main deploy kar sakta hoon"
🔁 GitOps Operator	m7+incident+m75 PASS	"maine prod-style incident handle kiya hai" ← yahi sabse heavy line hai
👁️ All-Seeing	m8 PASS	"main system ko dekh sakta hoon, guess nahi karta"
🚀 Shipper	`check-capstone1-shortener.sh` PASS (Capstone I: Deployment+Service+ArgoCD+live round-trip)	"git push se prod tak, zero manual — aur machine ne verify kiya"
💪 Battle-Tested	`check-capstone2-microshop.sh` PASS (Capstone II: 3 services + inter-service DNS + Ingress)	"maine teen microservices wired kiye — DNS, matrix CI, GitOps sab"

🔥 Streak — roz ka minimum¶

Rule ek hi hai: har din kam se kam 1 PROOF. Proof = koi bhi ek:

ek check script pass (naya ya re-run after fix)
ek lab ka ✅ success-check khud reproduce kiya
ek flashcard deck cold run (17)
ek recall gate bina notes ke solve

30 minute kaafi hain. Zero-proof din = streak reset. Travel/sick? Ek "freeze" per week allowed (insaan ho). Streak progress.md me khud likho — kisi app ki zaroorat nahi, imaandaari ki hai.

The 15-minute stuck rule (motivation ka असli killer boredom nahi, stuck hona hai)

15 min se zyada atke ho to escalate karo — isi ORDER me: (1) check script ka hint dobara padho (2) us module ka troubleshooting section (3) Incident Playbook ka symptom index (4) error message ko exact quote me search karo (5) aaj chhodo, kal ka pehla kaam yahi — fresh dimaag 10x tez hota hai. Chhodna ≠ failure; loop me phansna failure hai.

Solo mat khelo (2x completion ka cheat code)¶

Ek accountability partner dhundo — colleague, dost, koi bhi jo seekh raha ho. Weekly 30-min call, sirf 3 sawaal:

Is hafte kaunse checks PASS kiye? (screen share karke script chalao — live)
Kahan atke the aur kaise nikle? (yahi war stories ban jaati hain)
Agle hafte ka target kya hai? (bol dena = commit kar dena)

Partner nahi mila? Public commit karo — LinkedIn/Twitter pe har badge post karo, proof line ke saath. Audience hi partner hai. (Bonus: recruiters yahi posts dekhte hain.)

Start here — abhi, 10 minute me¶

git clone https://github.com/grvtech1/devops-handbook.git
Jo module last padha tha, uska check script chalao: bash labs/check-*.sh
❌ aaya? Perfect — wahi tumhara aaj ka kaam hai. Hint follow karo.
✅ aaya? Proof line progress.md me paste karo. Streak Day 1. 🔥

Ye platform tumse ek hi promise karta hai: yahan "complete" ka matlab scripts ne verify kiya hota hai. Isliye jab tum bologe "mujhe GitOps aata hai" — tumhare paas commit history, passing checks, aur ek incident drill ka proof hoga. Wahi difference hai course kiya aur kaam kiya me.

← Study Plan My Progress →