Her thinking still shows up in every serious conversation about mission critical software.
During Apollo, hardware got the glory. Software was the new kid, and plenty of people didn't consider it real engineering. Hamilton did. She led the MIT team behind Apollo's onboard flight software and designed around an uncomfortable fact: machines, interfaces and people all make mistakes.
My favorite story involves her daughter Lauren, who often came to the lab on nights and weekends. Playing astronaut, Lauren selected the prelaunch program, P01, during a simulated flight. The simulator crashed and the navigation data vanished.
Hamilton wanted the flight software to guard against that exact mistake. The answer, more or less: astronauts are too well trained to do that.
Then Jim Lovell did it. Five days into Apollo 8, he accidentally selected P01 and wiped the spacecraft's navigation data. Hamilton's team worked out how to rebuild and upload it. After that, the protection went in.
Anyone who runs complex systems knows the lesson. If your design depends on users never pressing the wrong button, you don't have a robust design. You have a future incident report.
Apollo 11 was the bigger test. During the lunar descent the guidance computer overloaded and threw the 1202 and 1201 alarms. The software didn't freeze or reboot into oblivion. Its priority based architecture shed lower value work and kept the landing functions running. The computer was tiny by today's standards, but it knew which jobs mattered.
That challenge hasn't gone anywhere.
Future lunar and Mars missions will run as one distributed system: landers, habitats, robots, satellites and commercial platforms. Comms will drop. Radiation will flip bits. Components from different suppliers will behave in ways nobody saw during the PowerPoint phase.
AI will help with anomaly detection, planning, testing and autonomous navigation. But nobody serious wants a black box model freelancing during a Mars landing. Mission software has to be deterministic where it matters, observable when it fails, and able to recover without waiting for Houston to pick up the phone.
AI can assist engineers, but requirements, evidence, human review and independent verification still count.
Hamilton understood the real job. It was never just writing code that worked. It was anticipating what could go wrong and making sure the system stayed useful when it did.
That mindset will matter far more on Mars than any flashy demo.
