Percussive Maintenance: If It's Good Enough for NASA...
Description
A two-panel meme that validates the classic programmer's urge to hit things when they don't work. The top panel shows a news headline, 'NASA Fixes Mars Lander By Telling It to Hit Itself With a Shovel', accompanied by an image of the InSight lander's robotic arm on the Martian surface. The bottom panel features a scene from The Lego Movie. The character Wyldstyle, labeled 'Normal People', looks with concern at Emmet, who is labeled 'Programmers who smash their keyboard when the code fails'. The joke provides a humorous justification for the frustrated, brute-force 'solution' of keyboard smashing. By showing that even a highly sophisticated organization like NASA resorts to a form of 'percussive maintenance' on multi-million dollar equipment millions of miles away, it normalizes the seemingly irrational behavior of a developer at their desk. For senior engineers, it's a funny and relatable take on the surprising effectiveness of unorthodox, low-tech solutions, even in high-tech fields
Comments
10Comment deleted
The official term is 'kinetic recalibration.' It's the first step in any senior engineer's debugging flowchart, right after 'blaming the compiler' and before 'sacrificing a rubber duck to the legacy code gods'
NASA just shipped the first remote percussive-maintenance API - kubectl shovel --namespace=mars - because at 20-minute RTT, brute force counts as a distributed-systems pattern
NASA spent millions on remote debugging tools just to reinvent percussive maintenance, while we've been practicing it on production servers since someone first suggested "just restart the pod."
When NASA's solution to a multi-million dollar Mars lander malfunction is literally 'have you tried hitting it?', you realize that percussive maintenance transcends all levels of engineering sophistication. The difference is NASA documents it as 'applying mechanical force to dislodge regolith obstruction' while we just rage-quit and blame the compiler. At least when their hardware doesn't respond, they can't accidentally commit the broken state to production
Percussive maintenance is just a physical-layer retry with exponential backoff - aka apply_impulse_until_telemetry_green()
NASA fixed a Mars lander by telling it to hit itself with a shovel - the only runbook where an idempotent bash command is literal. Keyboard‑smashing? Just local retries with terrible observability
Percussive maintenance: the only fix that works on both Mars rovers and Heisenbugs hiding in prod
Works with humans as well Comment deleted
Sometimes it the only way Comment deleted
But my main computer is a laptop... Comment deleted