Chapter 02 — The Transformation

Executor
to
Architect

This page is a living document — updated as the journey happens, not after it's over. No polished retrospective. No success story written in hindsight. Just the real thing — week by week, including the hard weeks.

Active — Started 28 May 2026
· 24 weeks · 430 hours · Updated weekly
The Honest Truth

Why this
exists

11 years in tech. 6 in DevOps. And for most of it I was doing exactly what I was told — executing tasks, closing tickets, moving on. The bull tied to the cart. Useful, reliable, going in circles.

I was never asked to design. Never asked why. Just how fast and how clean. Good at it, yes. But that's not enough anymore — not for where I want to go, not for who I want to become as an engineer.

This journey is about building the thinking I never built in 11 years. Not just more tools. Not just more certs. A complete rewiring of how I look at systems.

I'm documenting it publicly because accountability matters, and because every DevOps engineer who's felt exactly this way deserves to see someone do it honestly — not the curated version.

The single rule
"Never just build. Always answer three questions first: Why does this exist? What problem does it solve? What breaks if it's wrong?"
The commitment
"2 hours daily. 3–4 hours on weekends. 430 hours over 6 months. Every hour active building — not watching, not reading, not planning."
The goal
"Not a job. Not a cert. An architect mindset. The ability to walk into any system and understand it — then improve it — before touching anything."

The 24-Week
Roadmap

430 hours · 6 phases
28 May → Nov 2026
Active Phase 1 — Foundation Sprint Jun – Jul 2026 · Weeks 1–8
Week 01 · 28 May
Linux Internals — Read the system, don't just use it
Output: Process map, break-and-fix log, paragraph explanation
Week 02 · 04 Jun
Linux Networking — iptables, NAT, DNS from first principles
Output: Trace a web request end-to-end on paper
Week 03 · 11 Jun
Git Internals — What Git actually is under the hood
Output: Branching strategy doc for 10-engineer team
Week 04 · 18 Jun
Python automation — GHAS audit CLI tool
Output: GitHub API script — repo GHAS status CSV exporter
Week 05 · 25 Jun
Containers — security and architecture lens
Output: Audit 5 public Dockerfiles, rewrite one from scratch
Week 06 · 02 Jul
CI/CD — design before implementation
Output: 50-service CI/CD architecture on paper, then GitHub Actions
Week 07 · 09 Jul
CI/CD — secrets, promotion, rollback mechanisms
Output: Full pipeline with env promotion and rollback tested
Week 08 · 16 Jul — Buffer / Catch-up Week Intentional slack. Life happens. Use it.
Upcoming Phase 2 — The Platform Layer Aug – Sep 2026 · Weeks 9–16
Week 09 · 23 Jul
Kubernetes — local cluster, raw mechanics
Output: Multi-tier app on k3d with probes, limits, HPA
Week 10 · 30 Jul
Kubernetes — break it systematically
Output: Node kill, memory exhaust, NetworkPolicy debug log
Week 11 · 06 Aug
Kubernetes — RBAC and multi-tenancy
Output: 3-team namespace isolation with full RBAC policies
Week 12 · 13 Aug
AKS — move to managed, understand the difference
Output: Same app on AKS, document what the managed plane hides
Week 13 · 20 Aug
Terraform — provision AKS, feel drift pain
Output: AKS cluster via Terraform, manual drift introduced and fixed
Week 14 · 27 Aug
Terraform — modules and boundaries
Output: Refactored into networking/cluster/security modules
Week 15 · 03 Sep
Terraform — remote state, locking, team scenarios
Output: State in Azure Storage, lock broken intentionally, documented
Week 16 · 10 Sep — Buffer / Catch-up Week Intentional slack. Use it.
Upcoming Phase 3 — Security + Observability Oct 2026 · Weeks 17–20
Week 17 · 17 Sep
DevSecOps — GHAS beyond the docs
Output: Extended GHAS audit tool with Dependabot + risk scoring
Week 18 · 24 Sep
Secret management — Vault fundamentals
Output: Vault integrated into CI/CD pipeline
Week 19 · 01 Oct
Observability — SLOs not dashboards
Output: Prometheus + Grafana on AKS, SLO doc with breach alerts
Week 20 · 08 Oct
Observability — OpenTelemetry and tracing
Output: Distributed traces wired to the demo app
Upcoming Phase 4 — Architect Capstone Oct – Nov 2026 · Weeks 21–24
Week 21 · 15 Oct
IDP Design — architecture decisions on paper first
Output: Architecture Decision Records for full platform
Week 22 · 22 Oct
IDP Build — GitHub org + GHAS + AKS via Terraform
Output: Terraform-provisioned GitHub org with GHAS policies
Week 23 · 29 Oct
IDP Build — CI/CD + secrets + observability wired together
Output: Full pipeline from commit to AKS with SLO monitoring
Week 24 · 05 Nov
Capstone complete — documentation, README, open source ready
Output: Public GitHub repo — complete IDP reference architecture
The Real Test

Architect
Questions

Each week has one question. The question tests thinking, not tool knowledge. Answers written here after each week. Month 5 I read month 1 answers — the gap is the growth.

Week 01 — Linux
"What happens between the moment I type kubectl apply -f deployment.yaml and the moment my pod is running?"
Answer being written this week...
Week 03 — Git
"For a 10-engineer platform team, would you use trunk-based development or GitFlow? Under what conditions would you switch?"
Pending — Week 03
Week 05 — Containers
"A developer wants to push a Docker image directly to production. Design the policy, the technical control, and the enforcement mechanism that prevents this."
Pending — Week 05
Week 11 — Kubernetes
"Design a namespace structure for 3 teams on a shared cluster with complete isolation. What breaks at 10x scale?"
Pending — Week 11

Posts from the Journey

One post every two weeks — tied to what was just built, not written in isolation

Week 01 "What 11 years in DevOps didn't teach me about Linux" Coming soon
Week 03 "Git is not a version control tool — it's a graph database" Coming soon
Week 04 "I built a GHAS audit tool in Python — what I learned about writing real automation" Coming soon
Week 05 "I audited 5 public Dockerfiles — results were worse than I expected" Coming soon
Week 06 "How I'd design CI/CD for a 50-service company — starting with paper, not YAML" Coming soon
Week 10 "6 things I intentionally broke in Kubernetes to understand how it actually works" Coming soon
Week 13 "Terraform state is not a file — it's a contract" Coming soon
Week 17 "GHAS beyond the docs — what we learned running it across 10,000 repos" Coming soon
Week 22 "I built a complete Internal Developer Platform from scratch — here's the architecture" Coming soon
Week 24 "6 months from executor to architect — what actually changed" Coming soon