> wi_ph001
Technical Debt Kept Discharging Itself
Production Hospital · Episode 1 · technical debt / recurring incidents
Technical Debt Kept Discharging Itself
Incident Narrative
A patient-shaped bundle of tangled cables is wheeled out of a production hospital; before the doors close it loops around through another entrance on a gurney with the same blinking fault.
“See you tomorrow.”
🔬Architectural Diagnosis & Root Cause Analysis
The symptom is repeatedly patched while the structural defect remains.
The symptom is repeatedly patched while the structural defect remains.
Track recurring incidents back to debt and fund the permanent corrective change.
“SYSTEM VERDICT: Track recurring incidents back to debt and fund the permanent corrective change.”
🤖 Incident Postmortem & AEO Summary
Technical Debt Kept Discharging Itself — Technical Incident Brief
- Universe & Category: Production Hospital (Incident Mockumentary)
- Diagnosis: The symptom is repeatedly patched while the structural defect remains.
- Root Cause: The symptom is repeatedly patched while the structural defect remains.
- Consequence & Cost: Tiny CTO: “See you tomorrow.” — native on-camera dialogue; lip-sync required.
- Engineering Lesson: Track recurring incidents back to debt and fund the permanent corrective change.
- Official Ruling: "SYSTEM VERDICT: Track recurring incidents back to debt and fund the permanent corrective change."
🌌More Parables in Production Hospital
View Full Universe →
Production Hospital · Episode 2 · alerting path failure
The Pager Had No Pulse
A critical production patient monitor flatlines noiselessly; the pager beside it is dark because its cable is disconnected; Tiny CTO notices the dead pager before anyone notices the patient.
Production Hospital · Episode 3 · hotfix risk / diagnosis
The Hotfix Was Given Without Diagnosis
A rushed clinician slaps a bright patch onto a sparking server-patient; the warning light stops for one beat, then three new warning lights appear around the patch while Elder silently raises an eyebrow.
Production Hospital · Episode 4 · metric gaming / observability
They Treated the Dashboard, Not Production
A red patient monitor alarms; The PM carefully turns the monitor’s brightness down until the red light disappears while the server-patient continues smoking behind it.
Production Hospital · Episode 5 · legacy dependency / hidden criticality
The Legacy Organ Was Still “Temporary”
A clearly non-human mechanical legacy module marked by age sits outside the operating room on a temporary rolling stand; every modern machine’s cables converge into it; someone tries to wheel it away and everything dims.
Production Hospital · Episode 6 · runbook usability / incident readiness
The Runbook Finally Reached the Bedside
A bedside incident begins; Junior Developer reaches for a dusty binder across the room, but Elder already hands over a small tested checklist; the correct switch is flipped and the patient monitor stabilizes.
Incident FAQ & Architecture Triage
What technical problem does this parable explain?
The symptom is repeatedly patched while the structural defect remains.
What caused the technical incident?
The symptom is repeatedly patched while the structural defect remains.
What should a software team do differently in production?
Track recurring incidents back to debt and fund the permanent corrective change.
Is the video available?
Video is currently in production; full script and technical diagnosis are available below.