# Reflection: Naming Your Gaps While They're Still Cheap to Close

You just worked through twenty independent `kubectl` tasks. Before moving on, take a few
minutes to consolidate what actually stuck versus what you'd need to look up again.

## Reflection questions

1. Which THREE of these twenty commands do you feel genuinely confident using again right now,
   without a hint? Name them specifically.
2. Which ONE command surprised you the most — either because you didn't know it existed, or
   because it did something different than you expected?
3. `kubectl explain`, `kubectl patch`, and JSONPath output are commands a lot of engineers never
   learn early and end up rediscovering the hard way, mid-incident, years later. Now that you've
   used all three, where do you think you'd actually reach for one of them in a real debugging
   situation?

## Real Ops takeaway

**Fluency gaps are cheap to close now and expensive to close later.** Right now, not knowing
`kubectl patch` costs you a few minutes rereading this module. In a live incident six months
from now, not knowing it costs you minutes you don't have while a Service is down. Naming your
gaps here, while the stakes are zero, is how you make sure you close them before they matter.

**Breadth practice is not busywork.** It's easy to dismiss twenty small tasks as less valuable
than one big project — but the twenty small tasks are what make the big project fast to execute
later. This is the same discipline you'll rely on for the rest of ROOT_: build the vocabulary
now, apply it under pressure later.

This module is complete. Continue to the next module.

## Instructor Notes

**Discussion questions for a live classroom:** question 3 works well as a round-robin — go
person to person and have each name a different command, so the group collectively surfaces
most of the twenty rather than converging on the same one or two obvious answers.

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

**Expected takeaway:** Students should leave this module able to name their own remaining gaps
specifically, not just feel generally "done" with kubectl basics.