# Margaret Hamilton

> 1936– · Software Engineer
>
> **Recorded contribution:** Apollo guidance software; coined "software engineering"; priority scheduling

## How to use this dossier

Read for a causal chain, not a hero story: inherited problem → contribution → mechanism → downstream capability → limit. Then close the page and complete the reconstruction exercise from memory.

## 1. Historical orientation

Margaret Hamilton (born 1936) led the onboard flight-software effort for Apollo at MIT's Instrumentation Laboratory. Her teams built command- and lunar-module software under severe memory, timing, and reliability constraints, using priority scheduling, restart protection, extensive simulation, and rigorous interface analysis. During Apollo 11's landing, executive-overflow alarms appeared when a radar interface generated excess work; the software discarded lower-priority tasks and preserved landing-critical work. Hamilton popularized 'software engineering,' but claims that she alone coined the phrase are disputed and earlier printed uses exist. Her defensible achievement is leadership and systems-software design within the vast MIT, NASA, contractor, astronaut, and hardware effort.

## 2. The problem inherited

A small real-time computer had to manage guidance and control during a mission where missed deadlines, overloaded interfaces, or unrecoverable faults could be fatal and software could not be patched casually in flight.

## 3. The central contribution

Hamilton's division developed fault-aware real-time flight software whose scheduling, alarms, restart points, and validation preserved critical functions under overload and operator-interface error.

## 4. Reconstruct the mechanism

1. Assign jobs fixed priorities based on mission criticality and let urgent work preempt less important activity.
2. Track limited core sets and report executive overflow when more runnable work exists than the scheduler can retain.
3. Discard or postpone lower-priority jobs while preserving protected state and restart points for essential computations.
4. Exercise software, hardware, astronauts, and operating procedures together in simulation to expose interface and timing failures.

## 5. What changed downstream

- Apollo flight software demonstrated robust real-time scheduling and recovery in a safety-critical embedded system.
- The program strengthened software assurance, system-of-systems testing, and recognition of software engineering.
- Hamilton's recovered history broadened public understanding of women's technical leadership in the space program.

## 6. Attribution, limits, and uncertainty

- The onboard software was written and verified by large teams; Hamilton was a leader, not the sole programmer.
- Apollo 11's successful alarm response depended on hardware, executive design, mission procedures, and human decisions.
- The claim that Hamilton coined 'software engineering' should be phrased as advocacy/popularization unless stronger primary evidence is supplied.

## 7. Reconstruction lab

Simulate a fixed-priority scheduler with landing control, display, telemetry, and radar jobs. Overload it with radar requests, compare FIFO and priority scheduling, and implement restart points. Report which deadlines are met and which work is safely abandoned.

## 8. Evidence trail

- [Margaret Hamilton](https://history.nasa.gov/wp-content/uploads/static/history/alsj/a11/a11Hamilton.html) — NASA History Office
- [Margaret Hamilton: Apollo Software Engineer](https://www.draper.com/media-center/news-releases/detail/23333/margaret-hamilton-apollo-software-engineer-named-a-fellow-by-computer-history-museum) — Draper

---

*Research checked 2026-08-09. Dates, roles, and claims about living people are historical snapshots. Linked sources remain the authority; this dossier is original instructional synthesis.*