04/12/2026
When Margaret Hamilton arrived at MIT in the early 1960s, the word "software" barely existed as a concept.
Rockets were real. Engines were real. Hardware you could hold in your hands and test with instruments — that was real engineering. The code that told the machines what to do? That was paperwork. Administrative. An afterthought so minor that the people writing it were rarely taken seriously.
Margaret Hamilton decided that was going to change.
She had a mathematics degree, a mind that worked differently from almost everyone around her, and — because childcare options for working mothers in 1960s America were essentially nonexistent — a young daughter named Lauren who sometimes came with her to the lab.
One evening, Lauren sat down at the flight simulator and began pressing buttons. Playing astronaut.
The simulation crashed.
Most people would have sighed, reset the machine, and moved on. Hamilton didn't move on. She looked at what her daughter had accidentally triggered and asked a question no one at NASA had seriously considered yet:
What happens if a real astronaut does something like that — in space, during a critical maneuver, with no way to reset?
She took that question to her supervisors. They told her not to worry. Astronauts were the most rigorously trained professionals in the world. They didn't make mistakes like that.
Hamilton built the system anyway.
She developed a software architecture built around asynchronous priority scheduling — a system that could detect when the computer was being overwhelmed, identify which tasks were critical to survival, shed everything else, and keep flying. It was, at the time, a radical idea: software designed not just to perform, but to recover. To make intelligent decisions under pressure when humans couldn't.
She also gave the entire discipline its name. Margaret Hamilton coined the term "software engineering" — deliberately choosing words that demanded the field be taken as seriously as any branch of hardware or mechanical engineering. She understood that what she was building deserved a name equal to its importance.
Nobody fully understood how right she was until July 20, 1969.
Apollo 11. The Sea of Tranquility. Neil Armstrong and Buzz Aldrin descending toward the lunar surface for the first time in human history. And then — with the whole world watching — the alarms started.
1202. 1202.
The onboard computer was being overwhelmed with data from a radar system that had accidentally been left running. Inside Mission Control, tension spiked. The landing was seconds from being aborted. Everything — years of work, billions of dollars, the most watched moment in television history — balanced on what happened in the next few seconds.
Hamilton's code did exactly what she had built it to do.
It identified the radar data as non-essential. It shed it cleanly. It protected every function critical to the landing and kept the descent on track. Mission Control, understanding what had just happened, gave three words that echoed across the planet.
"Go for landing."
And moments later, a boot pressed into lunar dust for the first time in human history.
Back at MIT, there was a photograph taken of Margaret Hamilton standing beside a physical printout of the Apollo guidance software she had written and directed. The stack of paper reached above her head — taller than she was — representing every line of code, every contingency, every quiet decision made in a lab where she was rarely taken seriously.
She was smiling.
She had every reason to.
For decades afterward, the story of Apollo 11 was told through the astronauts, the mission controllers, the rocket engineers. Hamilton's name was known inside the field — but to the wider world, the woman who wrote the software that saved the landing was largely invisible.
That began to change slowly. Then all at once.
In 2016, President Barack Obama placed the Presidential Medal of Freedom — the highest civilian honor in the United States — around Margaret Hamilton's neck. She was 79 years old. The recognition was decades overdue and she accepted it with the same quiet dignity she had brought to every room that had underestimated her.
She was a mathematician and a mother who brought her daughter to the lab because she had no other option — and that daughter's accidental button-pressing sparked an idea that kept three astronauts alive and made the Moon landing possible.
She named an entire engineering discipline. She proved that the most important systems are not the ones that work perfectly — they are the ones that know what to do when things go wrong.
And she did all of it in a field that called her work "women's work."
The Moon landing happened 55 years ago. Her code worked perfectly.
That's not a coincidence. That's Margaret Hamilton.
