Margaret Hamilton died on September 30 at age 90, and the obituary practically writes itself: the woman who saved Apollo 11, the famous photo next to the stack of code printouts, the Presidential Medal of Freedom. All true. But the more interesting story is the one that runs underneath the highlight reel — a career-long campaign to force the world to take software seriously as engineering, not as some secondary craft practiced by people who couldn't build real hardware. Hamilton arrived at MIT in 1959 with a math degree from Earlham College and no formal training in computing, because almost nobody had formal training in computing. Her first job was writing weather prediction software for Edward Lorenz — the same Lorenz whose later work on chaos theory would reshape how we understand dynamical systems. From there she moved to Lincoln Laboratory's SAGE air defense project, where she began thinking about something almost nobody else was thinking about: software reliability. The idea that code could be systematically engineered to anticipate and prevent its own failures was, at the time, considered amusing. The Apollo work is where Hamilton's instinct for defensive programming became mission-critical, literally. The Lauren error episode is instructive: her four-year-old daughter crashed the command module simulator by activating a pre-launch program mid-flight. Hamilton proposed a software fix. She was overruled — astronauts would never make that mistake. Jim Lovell made exactly that mistake on Apollo 8. After that, Hamilton's proposed changes were integrated. The pattern — Hamilton identifies a failure mode, is told it's unnecessary, watches the failure occur, then gets the fix approved — is a template that software engineers will recognize from every organization they've ever worked in. The Apollo 11 moment is genuinely extraordinary. Moments before lunar landing, the computer threw a 1202 alarm — system overload caused by a hardware switch fault. Hamilton's priority-driven software architecture shed non-essential tasks to keep the landing sequence running. Houston trusted the software. Two men walked on the moon. This wasn't luck or heroism; it was the product of a design philosophy that treated error handling as a first-class concern rather than an afterthought. After Apollo, Hamilton left MIT when the Instrumentation Lab spun out to become Draper Laboratory. She founded Higher Order Software in 1976 and Hamilton Technologies in 1986, both built on her core conviction: that software systems should be engineered for error prevention and fault tolerance from the ground up. Her Universal Systems Language (USL) was the commercial expression of ideas she'd been developing since the 1960s. Over 130 publications across her career. The cultural afterlife is its own phenomenon. The photo of Hamilton standing next to the Apollo code printout — taller than she was — became a viral image decades after it was taken. The Apollo source code went up on GitHub in 2015. She became a Lego Minifigure in 2017, from a set designed by MIT's Maia Weinstock. The 2016 Presidential Medal of Freedom from Obama cemented a public recognition that was, in many ways, overdue by decades. What Hamilton actually built was not just flight software but an argument: that writing code is engineering, that the people who do it deserve the same professional standing as the people who design bridges or airframes, and that the discipline's core challenge is not cleverness but reliability. She started using the term 'software engineering' when it was treated as a joke. She lived long enough to see it become the default description for one of the most consequential professions on earth. She is survived by her daughter Lauren, son-in-law Richard Selesnick, two grandsons, and four great-grandchildren.
