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.
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.
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'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.
> 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.
Its unimaginable to me that people think making this kind of stuff public is socially acceptable. You may as well post a picture of your latest bowel movement and tell people to go look at it.
What a loss!
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.
The pic here is often people's first intro to her https://news.mit.edu/2016/scene-at-mit-margaret-hamilton-apo...
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.
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.
> 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.
Threads:
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
(channel name is AI Slop for those not clicking the link.)