The Apollo Guidance Computer threw 1201 and 1202 program alarms during the 1969 lunar descent because the Executive ran out of resources: 1202 meant core sets were exhausted, 1201 meant VAC areas. Spurious interrupts from the rendezvous radar interface — a reference-signal mismatch, not a "stuck" radar — flooded the scheduler. The save wasn't magic priority scheduling erasing the problem. It was a tested restart mechanism that shed low-priority work and re-established essential guidance tasks, plus a ground team that understood the alarms. Jack Garman advised Steve Bales that the alarms were survivable; Bales called "go." The system recovered repeatedly while descending toward the Moon, which is roughly the software equivalent of rebooting your flight controls every few seconds and hitting the runway anyway. Worth noting: the piece carries a 2026 correction fixing four errors from its earlier version — the radar claim, the lone-hero attribution to Margaret Hamilton, Garman's affiliation, and the alarm codes. The recovery software was a team effort at the Instrumentation Laboratory, and the article is right that the durable lesson is tested recovery plus humans who know what the alarms mean. The AGC also had less memory than this quiz widget asking about your inner child.