On July 20, 1969, as the Apollo 11 lunar module descended toward the Moon’s surface, the onboard computer started throwing alarms. Three minutes to landing. Nobody at NASA knew whether to continue or abort. The software answered first: it identified the problem, dropped the non-essential tasks, and focused entirely on what mattered in that moment — landing. That wasn’t luck. Margaret Hamilton designed it that way.
Who Is Margaret Hamilton?
Born in 1936 in Indiana, Hamilton studied mathematics at Earlham College and arrived at MIT in 1960 to work on weather prediction software. She had no formal training in programming — almost nobody did at the time — but she learned by writing code from scratch with a rigor that few matched.
Her work on Project SAGE, an air defense system built to detect Soviet aircraft, gave her deep experience in real-time programming that would prove decisive. When MIT went looking for programmers for the Apollo program, Hamilton was the first hired.
The Most Demanding Software Ever Written
In 1965, Hamilton took over as director of the Software Engineering Division at MIT’s Instrumentation Laboratory. The mission was clear and brutal: write the code that would guide astronauts to the Moon and back, running on computers with less processing power than any modern smartphone.
There were no schools teaching software engineering. No manuals. Every problem had to be solved from the ground up. As Hamilton put it: “there was no choice but to be pioneers.” According to NASA Science, the result was a system extraordinarily robust for its time — capable of detecting errors, recovering from failures, and prioritizing critical tasks in real time. It’s what we’d now call a human-in-the-loop system: designed so that humans remain in control of the decisions that matter most.
The Apollo 11 Alarms
Three minutes before touchdown, the system started throwing error codes 1201 and 1202. Nobody knew what they meant in the moment. Hamilton’s team found the answer in their notes: the computer was overloaded and had activated the priority system — dropping lower-priority tasks to focus on the essentials.
The message that reached Neil Armstrong was brief: We’re go. They could land. Hamilton had anticipated exactly that scenario and built the software to handle it. As the Smithsonian Magazine reported, without that system, Apollo 11 would very likely have aborted the landing.
Software Engineering as a Discipline
Hamilton didn’t just write code — she fought to have that work recognized for what it was. In NASA’s world of the 1960s, software was seen as secondary to hardware. Hamilton argued it deserved the same rigor as any other engineering discipline, and she coined the term “software engineering” to name it. Her colleagues laughed at first. Over time, the term became the name of an entire field.
That same philosophy — building systems that anticipate failure before it happens — is precisely why the debate over whether AI will replace software developers keeps circling back to the same point: the judgment that Hamilton brought to Apollo isn’t something that gets automated easily.
The Photo That Says It All
In 1969, someone photographed Margaret Hamilton standing next to the printed listings of the Apollo 11 software. The stack of paper reaches her shoulder. That’s the code she and her team wrote. The image became iconic decades later, once the world began to understand what it represented.
In 2016, Barack Obama awarded her the Presidential Medal of Freedom. In 2019, Google used 107,000 mirrors in the Mojave Desert to project her image by moonlight. Recognition that came late — but came clearly.
This is the fourth and final installment of the Women Who Built Technology series. You can also read the entries on Radia Perlman, Ada Lovelace, and Grace Hopper.
