NASA's Artemis II mission returned safely to Earth in April 2026, marking the first crewed lunar flyby in over 50 years. The mission came on the 56th anniversary of Apollo 13, reminding us that space exploration success comes not from perfection but from relentless practice and preparation. Just as NASA's Mercury, Gemini, and Apollo programs built upon each other through 25 manned missions between 1961 and 1970, modern software development follows similar principles.

Between 1965 and 1966, NASA achieved a remarkable cadence of missions every 1-2 months, creating a well-oiled machine that not only met Kennedy's lunar landing goal but exceeded it five times. This institutional learning proved crucial when Apollo 13 faced catastrophic failure - the same muscle memory that saved that mission now enables NASA to replicate decades of lunar program expertise in just two Artemis flights. The parallel to modern software practices is striking: DevOps continuous delivery pipelines automate repeated deployment tasks, while Infrastructure-as-code provides both repetition and flexibility.

During Artemis II, engineers identified a temperature sensor anomaly in the final countdown hour but determined it was merely an instrumentation issue, not a battery problem. This highlights the importance of instrumenting systems while understanding context and cross-referencing signals. When the space toilet failed, astronauts worked with ground engineers to repair it rather than resort to backup solutions. Like NASA, we must practice problem-solving repeatedly so when real failures occur, we can snatch success from the jaws of failure. Excellence isn't what we do when everything works - it's what remains when it doesn't, because we've practiced for exactly that moment.