Patch cables tell stories if you label them honestly

Every cohort inherits a rack photo with half-readable tags. We ask learners to narrate an imaginary outage tracing the cables without touching configs. The exercise is deliberately tactile—DevOps foundations are not only YAML. In the next section, we compare two labeling schemes: poetic names ("sunrise-backhaul") versus boring operational ones ("tor-03-uplink"). The debate reveals how support engineers think versus how platform teams archive knowledge. We then move to automation: small scripts that emit consistent prefixes, but never overwrite human notes without review. The third paragraph covers how we anonymize real customer stories while keeping emotional fidelity. The closing paragraph states the limitation: if your data hall forbids photography, you substitute with high-fidelity diagrams—still useful, but less visceral.