Apollo 11’s lunar ignition code was literally called “Burn, baby, burn”
The preserved listing puts a radio-inspired title above shared flight-control logic, with later annotations clearly marked.
Apollo 11’s lunar-module ignition software came with a title that could have gotten a meeting called today: “BURN, BABY, BURN.” The preserved source listing puts that line immediately above the master ignition routine. The engine was allowed to have more personality than a progress bar.
The comments define the routine’s territory precisely. It handles events from a check within 45 seconds of ignition through 26 seconds afterward, when descent-engine programs throttle up. That is a very consequential stretch of code to encounter while expecting a collection of cute programmer Easter eggs.
Peter Adler and Don Eyles are named in the listing as the people who conceived, implemented and maintained the routine. The comments emphasize maintenance, too. Even lunar software had someone whose name belonged beside the thing when it needed attention. The emphatic maintenance credit gives somebody a name to attach to questions about this particular shared routine, even in a lunar program.
The machinery under the title is reusable. Several lunar-module programs select different tables, and the shared routine uses those entries for their particular constants and control transfers. The listing names the register WHICH as the way a caller identifies its table. Yes, WHICH, a variable name that manages to answer the question while the program tables supply the specifics for each caller.
That helps explain why the listing is worth opening beyond its famous heading. Copying the whole ignition sequence for each program would mean several places to understand and maintain. This routine concentrates the common work, while the tables hold the differences. A reader doesn’t need to translate every assembly instruction to recognize that bargain.
The memorable phrase also has a provenance wrinkle. The explanation connecting it to radio DJ Magnificent Montague appears in a later annotation, added in 2009, relaying an account from Eyles at an anniversary gathering. The title itself belongs to the original listing; the story explaining the title arrived with the preservation work. Mixing those dates would send a modern footnote back into a 1969 computer.
That distinction makes the archive more interesting. A preserved program can contain original comments, transcription notes and later recollections on the same screen. They are all useful, but they answer different questions. The code shows what the routine said. A recollection supplies the remembered inspiration. The later recollection can sit directly above the code without becoming something written during the original development of the flight program.
For anyone who runs systems, the practical attraction is seeing the human voice beside the exact boundary of a shared component. The joke catches the eye; the comments explain what starts here, what callers supply, and who owns it. Plenty of modern repositories manage the first part and leave the other three as an exercise for whoever gets paged.
There is still plenty this one file cannot establish about the entire guidance computer. It is a component, preserved through transcription, with its own calls and tables. The title gets you through the door. Following those references is where the next piece of the flight begins.
Houston, we have a function.