# Reflection: Where You Already Practiced This

You've now named the operating model behind most of what ROOT_ taught. Take a few minutes to
trace it back through your own experience in this program.

## Reflection questions

1. Pick one specific moment from ROOT 05-10 or ROOT 12 where you practiced a DevOps/platform
   engineering principle without it being labeled that way. Name the principle explicitly now.
2. If you were designing a platform team's "golden path" for deploying a new service safely,
   which THREE things from ROOT_ (health probes, RBAC, resource limits, NetworkPolicy, etc.)
   would you bake in as defaults rather than leave to each team to remember?
3. What's one thing about GitOps, CI/CD, Infrastructure as Code, or observability you're
   genuinely curious about, now that you have the Kubernetes foundation to eventually build
   hands-on skill in it?

## Real Ops takeaway

**The skills you already have transfer further than "just Kubernetes."** Desired-state
thinking, least privilege, evidence-based troubleshooting, and structured incident response
aren't Kubernetes-specific facts — they're how experienced platform engineers reason about ANY
complex system. Recognizing that transfer is what turns "I learned Kubernetes" into "I think
like a platform engineer."

**Honest scope beats fake completeness.** This course didn't pretend to teach you GitOps or
CI/CD hands-on today — it told you exactly what's missing and why, and pointed at what it would
take to build it for real. That's the same standard the rest of ROOT_ held itself to
throughout — a module that doesn't exist yet is more useful, honestly labeled, than one that
exists in name only.

This module is complete.

## Instructor Notes

**Discussion questions for a live classroom:** question 2 works well as a small-group exercise —
have groups compare their "golden path defaults" lists and discuss disagreements.

**Approximate timing:** 10 minutes live discussion; 8 minutes self-paced writing.

**Optional extension:** ask students to research (outside class) one real company's public
engineering blog post about their platform engineering practice, and bring one concrete example
to share next session.

**Expected takeaway:** ROOT_ built real, transferable engineering judgment — this module makes
that transfer explicit rather than leaving students to discover it on their own.