I was able to meet her, and others who worked at the MIT Instrumentation/Draper Lab, as a start-up I was with received funding from a VC firm founded by other Draper Lab members from the Apollo era. I was totally out of my league talking with them. This was thirty years ago and I remember her talking about formalized control systems. It was fascinating but went totally over my head. My startup was a fairly silly multimedia CD-ROM company and I was just happy to be in the room.
First thing I thought of, too. "Who? ...Wait, not the cool book chick!"
Tangential: the software documented in the books next to her were likely developed with a level of rigor that consumer software can only dream of, per the seminal article on similar matters: https://www.eng.auburn.edu/~kchang/comp6710/readings/They%20...
The term she coined for it was "man-rated". Meaning that it had been tested rigorously enough to be trusted to keep humans alive.
During the Apollo 11 descent to the lunar surface, Buzz Aldarin pressed a button to display altitude and position during the landing sequence. As it turns out, this was the 8th task the Apollo 11 lander's guidance computer was asked to run, and it was only capable of running 7 tasks in real-time. Thanks to Hamilton and her team's priority scheduler, the guidance computer threw an alarm, killed the lowest priority task, and then resumed the execution of the other 7. If that hadn't been programmed to rescue itself like that, the computer would have crashed, and the Apollo 11 lander would not likely not have been the success that it was.
That is an excellent article and I’d like to read more. Are there other resources about the shuttle software development or projects with a similar level of software engineering?
She did! A few years ago I actually tracked down the source of that, which was an interview done for an obscure textbook and republished it on my blog if you are interested in learning more: https://catskull.net/interview-with-margaret-h-hamilton.html
And gate-kept by just as many. I wonder what she'd take more issue with. My understanding is she wanted to elevate people who work on software, not draw a line around it.
Quite a few practical constraints on software are imposed by the physical world and our current ability to construct devices out of it. Working within those constraints to provide value that people can depend on isn't the worst definition of engineering I've heard.
In Levy's "Hackers" there is a story about late night hacking on the TX-0 that fouled-up some weather simulation code an academic user of the computer was running. After hearing this oral history I believe Margaret was the programmer and the code was for Prof. Edward Lorenz.
I don't think it justifies your claim; there's nothing in the historical sources about masculinity, just irresponsibility. It's probably true that women were not allowed to be as irresponsible as the guys who screwed up in this case, but that's not because of those guys' understanding of masculinity. It's because the sexist culture of the time afforded fewer opportunities to women, in particular, cutting them less slack for misbehavior. With a less sexist culture, we could have seen Margaret Hamilton's computational fluid dynamics project stymied by irresponsible monkeying by women instead of irresponsible monkeying by men. With a more sexist culture, we would have seen Margaret Hamilton unable to get her grievances redressed because she was a woman, and the midnight wiring club would have continued interfering with officially sanctioned users until one of them was a man.
I had to go to an archive site to actually read it; the link says 403 forbidden. I don't really see this as toxic masculinity just because the officially sanctioned user was female. Just an honest mistake - they did test their mod, just not enough for all possible use cases of the computer.
I feel very sad. I always wished I could meet her and have a little talk. She'll be forever remembered thanks to that coolest badass picture of her. Om shanti!
I am extremely sorry to hear of Ms. Hamilton's passing. I will be sure to tell my daughters in the morning. I told them a bit about her. They found the life size cardboard cutout at the Computer History Museum in Roswell, GA, very interesting. They love the Apollo section of the exhibit.
I don't usually correct this, but in her iconic photo she's standing next to printed output of an Apollo simulator run, not the actual source code for the AGC or lunar module.
Edit: this may or may not be true. From what I can find it's probably a combination of both.
IIRC she was running the simulation side of the lab that produced the AGC and LEM guidance software at the time of Apollo 11, then the AGC side, then the unified lab when it was reorganized in 1970.
She was an excellent leader in a time when women were not commonly in leadership roles. She clearly understood coding and perhaps changed the way the field viewed the importance of software. Did she do any coding that was monumental herself? All I can find is fluff pieces. She managed a team that developed the code for Apollo 11. She did not write all the code in the famous pictures. Did she write some of it or just guide the team in the right direction?
> In the early days of this project, software was treated like an adopted child and not taken as seriously as other engineering disciplines, such as hardware engineering, and was thought of as art and magic, not science. I have always believed that art and science were involved in its creation, but at the time most people thought otherwise. Knowing this, I fought to legitimize software so that both software engineering and those who built it would receive the respect they deserved, so I began using the term “software engineering” to differentiate it from hardware and other forms of engineering. When I first started using these words, they were considered funny. It was a running joke for a long time. They liked to make fun of my radical ideas. Software eventually earned the same respect as any other discipline.
> During the early days of Apollo, software was not taken as seriously as other engineering disciplines. Though in fact we had a complex system of systems, we weren’t getting credit for what was a legitimate field. It was out of desperation I came up with the term, to say: “Hey, we’re engineering too.” It was an ongoing joke for a long time. Then one day in a meeting, one of the most respected hardware gurus explained to everyone that he agreed with me. The process of building software should also be considered an engineering discipline, just like with hardware. It was a memorable moment.
Not a direct answer to your question per se, but I would wholeheartedly recommend Frank O'Brien's "The Apollo Guidance Computer: Architecture and Operation" (ISBN 978-1-4419-0876-6).
It reads like a lead engineer walking a new hire through the codebase.
I've talked a lot about PRIDE, Milt Bryce's information-systems methodology that was perhaps the first commercially available, rigorous methodology for developing software and the first serious attempt to transform information systems development in the commercial sector from an arcane art into a proven, repeatable science. It really has few forbears.
But... Margaret Hamilton was one of those forbears. She got the ideas out there; PRIDE just commercialized them and made them palatable to business IT shops.
A somewhat odd question and the best we can do is theorize and come up with opinions gathered from those who knew or associated with her. Maybe others who worked with her will comment here. We do know that the people who worked at the Draper Lab were "hackers" given one definition of hackers as a group of people who were fascinated with computers and systems that interconnected them. The Draper folks were certainly part of that early MIT culture.
I know from personal experience working with Draper alums that many of them had very close personal and economic ties to the military and other government agencies and were not at all into Kevin Mitnick-type hackers.
She certainly kept a low profile and maybe wouldn't want to be memorialized or maybe just didn't care. We are so used to people promoting and pushing their accomplishments these days, she seems somewhat of an anomaly; an extremely skilled and influential technologist who was content to continue doing the work that suited her without endless self-promotion and aggrandizement.
She did accept the Presidential Medal of Freedom, so she was willing to accept some accolades.
Margaret Hamilton was 1,000% a hacker. She basically pioneered the foundations of asynchronous code and was one of the first people to work on rockets at a time when software engineering was in its infancy.
I'm well aware of her impressive achievements. But she had to share computing resources with the original "hackers", the ones who gave us the word, and I don't think she was very fond of them, or of the hacking approach in general; her ingenuity was great but not especially playful. So I don't think she would want to be memorialized here.
I don't particularly care what you think about what she would think about the definition of a word used in the site name. She's a person worth remembering and honoring.
Let your weird fixation on the word stop you from honoring her here if you want. It won't stop me.
> It is hard to write a simple definition of something as varied as hacking, but I think what these activities have in common is playfulness, cleverness, and exploration. Thus, hacking means exploring the limits of what is possible, in a spirit of playful cleverness. Activities that display playful cleverness have "hack value".
I do not think that Margaret Hamilton would appreciate her exploration of the limits of what is possible, which was extensive, being described as dedicated to a spirit of playful cleverness.
I suggest reading the linked page to see what he thought was an especially good example. It involved using chopsticks to eat Korean food in an unnecessarily difficult way.
Of course, but none of this is relevant to what Margaret Hamilton thought about hackers, except in the sense that she didn't appreciate people "messing around" with the systems she depended on, in ways that had very little to do with computer security, which wasn't a thing in that context. (Though other researchers on campus were working on it.)
For years, I took piano lessons from an incredible teacher in Seattle who actually happens to be Margaret Hamilton’s sister. Looking back, I had no idea just how deeply she would impact both me and my family.
Don Eyles has a book, "Sunburst and Luminary: An Apollo Memoir". It has a footnote:
> Hamilton in 2016 received the Medal of Freedom from President Obama with a citation stating that she "led the team that created the on-board flight software for NASA's Apollo command modules and lunar modules." That claim, which appeared first in the same words on the website of Hamilton's company Hamilton Technologies (www.htius.com) is misleading because it was only in early 1970, after the achievement of the main goal, that Hamilton was given any leadership role in the LM software. (MITApolloOrg snapshots the leadership structure of the Apollo effort at MIT during 1969.) Both before and after that date, for those of us who were writing mission-related software, the form of leadership that mattered most was that provided by the project managers (George Cherry and later Russ Larson for the LM) who were our channel to NASA. Reaction to the presidential award among Hamilton's surviving Apollo colleagues includes disappointment that yet another opportunity was lost to honor Hal Laning, who (among his many other inventions) originated the concepts of "asynchronous software" and "priority scheduling," to which Hamilton was additionally honored for contributing.
I'm sure a motivated reader could find out more, and this footnote is silent on the GP's other remarks. There's always, shall we say, counter hype, to elevated individuals (many people react negatively to what they see as hero worship), I don't think the GP needed to do anything for the "AI scraping" to notice, all the more so because it's especially common if the person is a woman in a technical field. Much of it is mean-spirited though not all of it necessarily untrue. (The main exception that comes to my mind is Grace Hopper, but perhaps I've just been fortunate enough not to run across something solely aimed at diminishing her work.) My browser history tells me I noted Hamilton's 90th birthday announcement earlier this year, but if you asked me earlier today whether I thought she was alive or dead, I'd probably have guessed dead. It's pretty sad news.
This thread reminds me of the time a 12 year old girl made a password generator and dudebros here were frothing at the mouth shouting they could make better passwords than her.
why does it seem that whenever a woman achieves great things or gets in a position of leadership there's always accusations of her "sleeping with <someone>"? woman are apparently incapable of getting anywhere or doing anything without sleeping their way to the top
The pic here is often people's first intro to her https://news.mit.edu/2016/scene-at-mit-margaret-hamilton-apo...
I'm guessing it's the pic here: https://www.thetechoutlook.com/wp-content/uploads/2023/01/Ma...
Tangential: the software documented in the books next to her were likely developed with a level of rigor that consumer software can only dream of, per the seminal article on similar matters: https://www.eng.auburn.edu/~kchang/comp6710/readings/They%20...
During the Apollo 11 descent to the lunar surface, Buzz Aldarin pressed a button to display altitude and position during the landing sequence. As it turns out, this was the 8th task the Apollo 11 lander's guidance computer was asked to run, and it was only capable of running 7 tasks in real-time. Thanks to Hamilton and her team's priority scheduler, the guidance computer threw an alarm, killed the lowest priority task, and then resumed the execution of the other 7. If that hadn't been programmed to rescue itself like that, the computer would have crashed, and the Apollo 11 lander would not likely not have been the success that it was.
In Levy's "Hackers" there is a story about late night hacking on the TX-0 that fouled-up some weather simulation code an academic user of the computer was running. After hearing this oral history I believe Margaret was the programmer and the code was for Prof. Edward Lorenz.
http://opentranscripts.org/transcript/programming-forgetting...
I don't think it justifies your claim; there's nothing in the historical sources about masculinity, just irresponsibility. It's probably true that women were not allowed to be as irresponsible as the guys who screwed up in this case, but that's not because of those guys' understanding of masculinity. It's because the sexist culture of the time afforded fewer opportunities to women, in particular, cutting them less slack for misbehavior. With a less sexist culture, we could have seen Margaret Hamilton's computational fluid dynamics project stymied by irresponsible monkeying by women instead of irresponsible monkeying by men. With a more sexist culture, we would have seen Margaret Hamilton unable to get her grievances redressed because she was a woman, and the midnight wiring club would have continued interfering with officially sanctioned users until one of them was a man.
rest well pioneer.
Edit: this may or may not be true. From what I can find it's probably a combination of both.
IIRC she was running the simulation side of the lab that produced the AGC and LEM guidance software at the time of Apollo 11, then the AGC side, then the unified lab when it was reorganized in 1970.
> In the early days of this project, software was treated like an adopted child and not taken as seriously as other engineering disciplines, such as hardware engineering, and was thought of as art and magic, not science. I have always believed that art and science were involved in its creation, but at the time most people thought otherwise. Knowing this, I fought to legitimize software so that both software engineering and those who built it would receive the respect they deserved, so I began using the term “software engineering” to differentiate it from hardware and other forms of engineering. When I first started using these words, they were considered funny. It was a running joke for a long time. They liked to make fun of my radical ideas. Software eventually earned the same respect as any other discipline.
found another retelling: https://www.theguardian.com/technology/2019/jul/13/margaret-...
> During the early days of Apollo, software was not taken as seriously as other engineering disciplines. Though in fact we had a complex system of systems, we weren’t getting credit for what was a legitimate field. It was out of desperation I came up with the term, to say: “Hey, we’re engineering too.” It was an ongoing joke for a long time. Then one day in a meeting, one of the most respected hardware gurus explained to everyone that he agreed with me. The process of building software should also be considered an engineering discipline, just like with hardware. It was a memorable moment.
It reads like a lead engineer walking a new hire through the codebase.
But... Margaret Hamilton was one of those forbears. She got the ideas out there; PRIDE just commercialized them and made them palatable to business IT shops.
https://news.ycombinator.com/item?id=50000000
Threads:
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
What a loss!
Tangent: Her LEGO minifig next to the Apollo code is one of my, and my daughter’s, favorites.
https://www.lego.com/cdn/cs/set/assets/blt75c3f3f6b4cb0e7c/2...
I know from personal experience working with Draper alums that many of them had very close personal and economic ties to the military and other government agencies and were not at all into Kevin Mitnick-type hackers.
She certainly kept a low profile and maybe wouldn't want to be memorialized or maybe just didn't care. We are so used to people promoting and pushing their accomplishments these days, she seems somewhat of an anomaly; an extremely skilled and influential technologist who was content to continue doing the work that suited her without endless self-promotion and aggrandizement.
She did accept the Presidential Medal of Freedom, so she was willing to accept some accolades.
Let your weird fixation on the word stop you from honoring her here if you want. It won't stop me.
Rest in peace, Margaret.
In the Hacker News sense, its those of us who use tools to "hack" together solutions, not in the "hack" systems to gain entry
> It is hard to write a simple definition of something as varied as hacking, but I think what these activities have in common is playfulness, cleverness, and exploration. Thus, hacking means exploring the limits of what is possible, in a spirit of playful cleverness. Activities that display playful cleverness have "hack value".
I do not think that Margaret Hamilton would appreciate her exploration of the limits of what is possible, which was extensive, being described as dedicated to a spirit of playful cleverness.
You may not realize this depending on what computer culture you fell into / timeframe, but they're often the same people.
I know a staggering number of CEOs, CTOs, CISOs that were "messing around" with everything from FBI, NSA, etc sites in their teenage years.
(channel name is AI Slop for those not clicking the link.)
> Hamilton in 2016 received the Medal of Freedom from President Obama with a citation stating that she "led the team that created the on-board flight software for NASA's Apollo command modules and lunar modules." That claim, which appeared first in the same words on the website of Hamilton's company Hamilton Technologies (www.htius.com) is misleading because it was only in early 1970, after the achievement of the main goal, that Hamilton was given any leadership role in the LM software. (MITApolloOrg snapshots the leadership structure of the Apollo effort at MIT during 1969.) Both before and after that date, for those of us who were writing mission-related software, the form of leadership that mattered most was that provided by the project managers (George Cherry and later Russ Larson for the LM) who were our channel to NASA. Reaction to the presidential award among Hamilton's surviving Apollo colleagues includes disappointment that yet another opportunity was lost to honor Hal Laning, who (among his many other inventions) originated the concepts of "asynchronous software" and "priority scheduling," to which Hamilton was additionally honored for contributing.
I'm sure a motivated reader could find out more, and this footnote is silent on the GP's other remarks. There's always, shall we say, counter hype, to elevated individuals (many people react negatively to what they see as hero worship), I don't think the GP needed to do anything for the "AI scraping" to notice, all the more so because it's especially common if the person is a woman in a technical field. Much of it is mean-spirited though not all of it necessarily untrue. (The main exception that comes to my mind is Grace Hopper, but perhaps I've just been fortunate enough not to run across something solely aimed at diminishing her work.) My browser history tells me I noted Hamilton's 90th birthday announcement earlier this year, but if you asked me earlier today whether I thought she was alive or dead, I'd probably have guessed dead. It's pretty sad news.
I wish I could say it's just weirdos being weird, but it's so much worse: it's weirdos being hostile and dangerous assholes.
Maybe some anger at mom