05/27/2026
Great story about women in the space program.
When Margaret Hamilton arrived at MIT in the early 1960s, the word "software" barely existed as a recognized engineering concept.
Rockets were real. Engines were real. Hardware — things you could hold, test with instruments, verify through physical measurement — that was engineering. The code that told the machines what to do? That was closer to paperwork. Administrative. An afterthought so minor that the people writing it were rarely considered engineers in any serious sense.
Hamilton had a mathematics degree, a way of thinking about systems that set her apart from most of the people 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 at MIT.
One evening, Lauren sat down at the flight simulator.
She began pressing buttons. Playing astronaut.
The simulation crashed.
Hamilton didn't reset the machine and move on. She stood there and asked the question that would shape everything that followed: what happens if a real astronaut does something like that — in space, during a critical maneuver, with no way to reset?
She brought the question to her supervisors. They told her not to worry. Astronauts were the most rigorously trained professionals in the world. Accidental errors of that kind simply didn't happen.
Hamilton built the system anyway.
The software architecture she developed centered on a concept called asynchronous priority scheduling — a system capable of detecting when the computer was being overwhelmed with more tasks than it could handle, identifying which functions were essential to the survival of the mission, shedding everything else cleanly, and keeping flying.
This was, at the time, a genuinely radical idea. Most software was designed to perform tasks. Hamilton's software was designed to make decisions — to behave intelligently under pressure in situations that couldn't be fully anticipated in advance, recovering from unexpected conditions rather than failing when they occurred.
She also championed a name for what she and her colleagues were doing. Hamilton is widely credited with coining or popularizing the term "software engineering" within the Apollo program — deliberately selecting words that placed the discipline alongside hardware and mechanical engineering rather than treating it as something lesser. She understood that the field she was building deserved a name equal to its actual importance, and she insisted on that name at a time when most of the people around her found the argument premature.
Nobody fully understood how right she was until July 20, 1969.
Apollo 11. The Sea of Tranquility. Neil Armstrong and Buzz Aldrin 50,000 feet above the lunar surface and descending, with the whole world watching from Earth and Mission Control tracking everything that could go wrong.
Then the alarms.
The Apollo Guidance Computer was being overwhelmed. The abort radar — a system that should have been turned off before the powered descent began — had been accidentally left running, flooding the computer with data it hadn't been allocated resources to process. The computer was receiving more information than it could handle while simultaneously trying to land two human beings on a surface no machine had ever touched.
In Mission Control, every face that understood what the 1202 alarm meant went taut. The lunar landing — years of work, tens of thousands of people, the most watched moment in television history — was seconds from being aborted.
Hamilton's code did what she had built it to do.
It recognized that the radar data was non-essential to the landing. It shed it. It protected every function that was critical — guidance, navigation, control — and kept the descent running. The priority scheduling she had designed worked exactly as she had designed it to work, under conditions she had imagined precisely because her daughter had once pressed the wrong buttons on a simulator.
Mission Control, understanding what had just happened, gave three words.
"Go for landing."
Twelve minutes later, a boot pressed into lunar dust for the first time in human history.
Back at MIT, there is a photograph taken of Margaret Hamilton standing next to a physical printout of the Apollo guidance software — every line of code, every contingency, every decision made in years of work in a lab where her discipline had been considered administrative work.
The stack of paper is taller than she is.
She is smiling.
She had every reason to.
For decades after Apollo 11, the story of the Moon landing was told through the astronauts, the mission controllers, the rocket engineers. Margaret Hamilton's name was known within the field — honored by the people who understood what her software had done. To the wider world, she was largely invisible.
That changed 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 Hamilton's neck. She was seventy-nine years old. The recognition was decades overdue. She accepted it with the same quiet dignity she had brought to every room that had underestimated what she was building.
She was a mathematician and a mother who brought her daughter to the lab because she had no other option — and that daughter's afternoon of accidental button-pressing sparked a question that produced software critical enough to keep three astronauts alive and ensure the Moon landing succeeded.
She named an entire engineering discipline. She proved something that the history of complex systems has confirmed repeatedly since: the most important software is not software that works perfectly when everything goes right. It is software that knows what to do when things go wrong.
She built that software while working in a field that called what she was doing paperwork.
The Moon landing was July 20, 1969. Her code worked.
That is Margaret Hamilton.
