Skip to main content

How Margaret Hamilton Wrote the Computer Code That Helped Save the Apollo Moon Landing Mission

From a distance of half a century, we look back on the moon landing as a thoroughly analog affair, an old-school engineering project of the kind seldom even proposed anymore in this digital age. But the Apollo 11 mission could never have happened without computers and the people who program them, a fact that has become better-known in recent years thanks to public interest in the work of Margaret Hamilton, director of the Software Engineering Division of MIT's Instrumentation Laboratory when it developed on-board flight software for NASA's Apollo space program. You can learn more about Hamilton, whom we've previously featured here on Open Culture, from the short MAKERS profile video above.

Today we consider software engineering a perfectly viable field, but back in the mid-1960s, when Hamilton first joined the Apollo project, it didn't even have a name. "I came up with the term 'software engineering,' and it was considered a joke," says Hamilton, who remembers her colleagues making remarks like, "What, software is engineering?"

But her own experience went some way toward proving that working in code had become as important as working in steel. Only by watching her young daughter play at the same controls the astronauts would later use did she realize that just one human error could potentially bring the mission into ruin — and that she could minimize the possibility by taking it into account when designing its software. Hamilton's proposal met with resistance, NASA's official line at the time being that "astronauts are trained never to make a mistake."

But Hamilton persisted, prevailed, and was vindicated during the moon landing itself, when an astronaut did make a mistake, one that caused an overloading of the flight computer. The whole landing might have been aborted if not for Hamilton's foresight in implementing an "asynchronous executive" function capable, in the event of an overload, of setting less important tasks aside and prioritizing more important ones. "The software worked just the way it should have," Hamilton says in the Christie's video on the incident above, describing what she felt afterward as "a combination of excitement and relief." Engineers of software, hardware, and everything else know that feeling when they see a complicated project work — but surely few know it as well as Hamilton and her Apollo collaborators do.

Related Content:

Margaret Hamilton, Lead Software Engineer of the Apollo Project, Stands Next to Her Code That Took Us to the Moon (1969)

How 1940s Film Star Hedy Lamarr Helped Invent the Technology Behind Wi-Fi & Bluetooth During WWII

Meet Grace Hopper, the Pioneering Computer Scientist Who Helped Invent COBOL and Build the Historic Mark I Computer (1906-1992)

How Ada Lovelace, Daughter of Lord Byron, Wrote the First Computer Program in 1842–a Century Before the First Computer

Based in Seoul, Colin Marshall writes and broadcasts on cities, language, and culture. His projects include the book The Stateless City: a Walk through 21st-Century Los Angeles and the video series The City in Cinema. Follow him on Twitter at @colinmarshall, on Facebook, or on Instagram.

How Margaret Hamilton Wrote the Computer Code That Helped Save the Apollo Moon Landing Mission is a post from: Open Culture. Follow us on Facebook, Twitter, and Google Plus, or get our Daily Email. And don't miss our big collections of Free Online Courses, Free Online Movies, Free eBooksFree Audio Books, Free Foreign Language Lessons, and MOOCs.



from Open Culture https://ift.tt/2KxqHtg
via Ilumina

Comments

Popular posts from this blog

Board Game Ideology — Pretty Much Pop: A Culture Podcast #108

https://podtrac.com/pts/redirect.mp3/traffic.libsyn.com/secure/partiallyexaminedlife/PMP_108_10-7-21.mp3 As board games are becoming increasingly popular with adults, we ask: What’s the relationship between a board game’s mechanics and its narrative? Does the “message” of a board game matter? Your host Mark Linsenmayer is joined by game designer Tommy Maranges , educator Michelle Parrinello-Cason , and ex-philosopher Al Baker to talk about re-skinning games, designing player experiences, play styles, game complexity, and more. Some of the games we mention include Puerto Rico, Monopoly, Settlers of Catan, Sorry, Munchkin, Sushi Go, Welcome To…, Codenames, Pandemic, Occam Horror, Terra Mystica, chess, Ticket to Ride, Splendor, Photosynthesis, Spirit Island, Escape from the Dark Castle, and Wingspan. Some articles that fed our discussion included: “ The Board Games That Ask You to Reenact Colonialism ” by Luke Winkie “ Board Games Are Getting Really, Really Popular ” by Darron Cu...

Ishkur’s Guide to Electronic Music: An Interactive, Encyclopedic Data Visualization of 120 Years of Electronic Music

In a very short span of time, the descriptor “electronic music” has come to sound as overly broad as “classical.” But where what we (often incorrectly) call classical developed over hundreds of years, electronic music proliferated into hundreds of fractal forms in only decades. A far steeper quality curve may have to do with the ease of its creation, but it’s also a factor of this accelerated evolution. Music made by machines has transformed since its early 20th-century beginnings from obscure avant-garde experiments to massively popular genres of global dance and pop. This proliferation, notes Ishkur—designer of Ishkur’s Guide to Electronic Music —hasn't always been to the good. Take what he calls “trendwhoring,” a phenomenon that spawns dozens of new works and subgenera in short order, though it’s arguable whether many of them should exist. Ishkur, describes this process below in an excerpt from his erudite, sardonic “Frequently Unasked Questions”: If fart noises were sudde...

How Led Zeppelin Stole Their Way to Fame and Fortune

When Bob Dylan released his 2001 album  Love and Theft , he lifted the title from a  book of the same name by Eric Lott , who studied 19th century American popular music’s musical thefts and contemptuous impersonations. The ambivalence in the title was there, too: musicians of all colors routinely and lovingly stole from each other while developing the jazz and blues traditions that grew into rock and roll. When British invasion bands introduced their version of the blues, it only seemed natural that they would continue the tradition, picking up riffs, licks, and lyrics where they found them, and getting a little slippery about the origins of songs. This was, after all, the music’s history. In truth, most UK blues rockers who picked up other people’s songs changed them completely or credited their authors when it came time to make records. This may not have been tradition but it was ethical business practice. Fans of Led Zeppelin, on the other hand, now listen to their...