Margaret Hamilton: the woman who gave us the moon
When the first moon landing was on the brink of failure, her software came through for the win. Margaret Hamilton has died at the age of 90. The legacy she leaves behind stretches far beyond space travel.
Houston, 20 July 1969. In just a few minutes, the first moon landing in human history is set to take place. Neil Armstrong and Buzz Aldrin are descending towards the dusty surface of the moon. Underneath them: a strange, hostile world. Behind them: hundreds of thousands of kilometres of darkness. Back on Earth, millions of people collectively hold their breath.
Then, suddenly, an alarm goes off. The onboard computer is overloaded. Now, at the very moment the mission is entering its perhaps most critical phase, the technical equipment is on the brink of failure. Armstrong and Aldrin are forced to rely on instructions from Mission Control in Houston. Should they keep pushing on? Or abort the mission?
What the two astronauts have no way of knowing is that their computer’s software was developed specifically for situations like this. It can put aside unimportant tasks to focus on what really matters in the moment at hand. The landing. The astronauts’ survival. The fulfilment of one of humankind’s dreams. Another thing they’re unaware of at the time is that the mastermind behind this software is a fairly unknown woman.
Margaret Hamilton.
Source: Daphne Weld Nichols/CC BY-SA 3.0
She died on 30 September 2026. According to an obituary published by the Massachusetts Institute of Technology (MIT), she was 90 years old. With her passing, the world has lost one of the most significant pioneers in the history of computing. A woman who not only helped put people on the moon, but also changed our understanding of what software can do.
The woman behind the code
There’s a famous black-and-white photo from 1969. In it, a young woman is standing next to a stack of printed computer programs. The pile is almost as tall as she is. Margaret Hamilton is smiling casually at the camera, as if it’s nothing out of the ordinary.
And yet this mountain of paper holds a piece of human history.
Source: MIT Museum/Restored by Adam Cuerden
It’s the software that Hamilton and her team at MIT developed for the Apollo program. Thousands upon thousands of lines of code, written for computers whose processing power seems laughably low by today’s standards. Even so, they were set to make something possible that had previously only existed in science fiction novels: transporting people to another celestial body – and back.
To call her story extraordinary would be a gross understatement. Hamilton, born in 1936 in the US state of Indiana, studied mathematics – a rare field for women to enter at the time. Her early career took her into meteorology, where she developed weather forecasting programs. From there, she went on to MIT before eventually joining NASA’s Apollo program in 1965. Just a few years later, she was leading the teams responsible for the spacecrafts’ onboard software. She was only in her early thirties at the time.
Source: Lawrence Jackson/White House
But she wasn’t just young. She was also a woman in a male-dominated world, working in a field that, back then, wasn’t even taken seriously as a distinct branch of engineering. Software was seen as an afterthought. It was hardware – the machines and rockets – that were viewed as true engineering. Programs, on the other hand, were something you just had to write on the side.
Hamilton saw things differently.
She fought for software to be recognised as an integral part of complex technical systems. In fact, she used a term that’d illicit laughter from her contemporaries: software engineering. These days, nobody questions the phrase. Back then, it was practically revolutionary.
The art of anticipating the unknown
What made Hamilton’s work so extraordinary wasn’t just her technical skill. It was her way of thinking. She understood something that might sound obvious now, but certainly wasn’t back then: human beings make mistakes. And as a result, machines do too. So if you’re developing systems that human lives depend on, you can’t simply assume that everything will go well.
An anecdote from the history of the Apollo program illustrates this particularly well. One day, Hamilton’s four-year-old daughter, Lauren, was playing with a simulator in the MIT lab. As she did so, she accidentally triggered a program function that should never be activated during a spaceflight. The simulator crashed.
Hamilton immediately identified a danger. She wanted to prevent the same kind of error from occurring during a real-life mission. Her bosses, however, initially rejected her bid to modify the software. They argued that astronauts were exceptionally well-trained, and would never make that kind of mistake.
Then, there was Apollo 8. In December 1968, humans left Earth’s orbit for the first time to travel around the moon. On board was pilot Jim Lovell, who’d later command the famous Apollo 13 mission. Despite being one of NASA’s best astronauts, he accidentally activated the very function mid-flight that Hamilton had warned everyone about. Important navigation data was lost. Hamilton and her team had to help fix the problem. If it hadn’t been clear before, it certainly was now: Hamilton was right.
Source: NASA
This experience became fundamental to Hamilton’s work. Software couldn’t be something that only worked when everyone was following the rules. It had to keep working when someone made a mistake. When the unpredictable happened. When the very thing that nobody was expecting to happen, did.
The importance of this way of thinking became clear a few months later on the moon.
One small step, thousands of lines of code
Back to 20 July 1969. As Armstrong and Aldrin approach the surface of the moon, the onboard computer goes into overdrive. But instead of crashing completely, the software identifies tasks that are essential for landing. It puts less important processes on hold and continues to operate. Exactly as Hamilton and her team had planned.
Mission control gives the go-ahead, and the flight continues. Armstrong takes over manual control and looks for a suitable place to land. Fuel is running low. Seconds tick by. Then, finally, the words the whole world had been waiting for:
«Houston, Tranquility Base here. The eagle has landed.»
A few hours later, Neil Armstrong became the first person to ever set foot on the moon. Images of the event spread around the globe. And became a symbol of an entire era – proof that humanity could make even its boldest dreams a reality. Armstrong will live on forever. As will Aldrin. Their names will be recorded in history books, their faces will appear on stamps and their words will be passed down from generation to generation.
Margaret Hamilton, on the other hand, initially stayed pretty unknown. Although her work was partly what made it possible for those words to be spoken at all. Of course, she didn’t put people on the moon by herself. Apollo was the result of hundreds of thousands of people’s efforts. Those of engineers, mathematicians, technicians, scientists and astronauts. A tremendous collective effort, driven by knowledge, ambition, political will and, most importantly, enormous financial support.
But Hamilton’s contribution reminds us that history isn’t just written by the people who end up in front of the cameras. It’s also written by folks who ensure the cameras have something to capture in the first place.
I write about technology as if it were cinema, and about films as if they were real life. Between bits and blockbusters, I’m after stories that move people, not just generate clicks. And yes – sometimes I listen to film scores louder than I probably should.
Interesting facts about products, behind-the-scenes looks at manufacturers and deep-dives on interesting people.
Show all
