Summary
A structured 6-month roadmap for learning DevOps, arguing that 3 months is enough to watch tutorials but not to actually learn. The guide emphasizes fundamentals-first ordering: Linux (Month 1) → Networking + Git/CI-CD concepts (Month 2) → Docker (Month 3) → Cloud + IaC (Month 4) → Kubernetes basics (Month 5) → Deliberate failure practice + interview prep (Month 6). The goal is junior/entry-level readiness, not seniority.
一份 6 個月的 DevOps 學習路線圖，強調 3 個月只夠看教學影片，真正學會需要 6 個月。指南採用基礎優先的順序：Linux（第 1 月）→ 網路 + Git/CI-CD 概念（第 2 月）→ Docker（第 3 月）→ 雲端 + IaC（第 4 月）→ Kubernetes 基礎（第 5 月）→ 刻意練習失敗 + 面試準備（第 6 月）。目標是達到初級職位就業能力，而非資深工程師水準。
Key Points
- Month 1 — Linux fundamentals: processes, logs, services, crash behaviour — “most DevOps problems come down to the process died / port is wrong / config is missing”
- Month 2 — Networking (IPs, ports, DNS, HTTP, load balancers) + Git + CI/CD concepts (not Jenkins syntax, just the flow)
- Month 3 — Docker: containerize small apps, break them, fix them; trial-and-error beats tutorials
- Month 4 — Cloud (pick one: AWS/Azure/GCP) + Infrastructure as Code (Terraform as logical next step, not magic)
- Month 5 — Kubernetes: only the day-to-day subset (run, expose, update, debug); reading logs/events matters more than memorizing YAML
- Month 6 — Practice deliberate failures (broken deployments, crashing pods, failed pipelines); clean up projects; learn to explain what broke and why
- Interviews care more about how well you understand your projects than what you built
Insights
- The sequencing is load-bearing: Linux before networking before Docker before cloud before Kubernetes mirrors actual dependency order — each layer explains the one above it; jumping ahead makes everything feel like magic/mystery
- “You don’t need to learn everything” applied to Kubernetes is useful permission: the tool is vast, but day-to-day work uses a small subset; learning to debug is more transferable than learning all features
- Month 6 being about deliberate failure practice is underrated — most learning resources teach happy paths; the ability to reason about failures is what actually differentiates candidates in interviews
- The 3-month vs 6-month framing is a useful heuristic: 3 months = tutorial completion speed; 6 months = internalization speed; these are different things and conflating them leads to false confidence
- The DVC article in this vault is a concrete example of the Month 4 content (cloud storage, automation) — these topics connect directly
Connections
- DevOps
- Linux
- Docker
- Kubernetes
- CD
- Infrastructure as Code
- MLOPS Versioning Data With DVC
- Career Learning
Raw Excerpt
DevOps is not about speed. It’s about understanding how software behaves after it leaves your laptop.