“The Story of Mel, a Real Programmer” is a piece of computing folklore written by Ed Nather and posted to Usenet on May 21, 1983. It opens by quoting the macho claim, then circulating in the wake of Ed Post’s Datamation essay, that “Real Programmers write in FORTRAN,” and then offers Mel as living proof that the true Real Programmer worked even closer to the metal than Fortran. Nather had worked alongside Mel Kaye at the Royal McBee Computer Corporation, and the post is presented as a firsthand reminiscence.
Mel programmed the Royal McBee RPC-4000, a drum-memory machine. On such computers, both instructions and data lived on a magnetic drum that rotated continuously, and an instruction could not execute until the drum had spun the needed word under the read head. Mel refused to use the company’s optimizing assembler, which automatically arranged instructions to minimize this rotational delay. Instead he placed every instruction by hand, calculating exactly where on the drum it should sit so that the next instruction would arrive under the head at the precise moment it was needed. His hand-tuned code ran faster than anything the optimizer could produce.
The legend’s centerpiece is a loop that Nather could not understand. Tasked with modifying one of Mel’s blackjack programs, Nather found a loop with no apparent exit test, yet it terminated correctly every time. After long study he discovered that Mel had exploited an overflow: as an address index incremented, it would eventually overflow into the instruction’s operation-code field, transforming the instruction itself into the jump that ended the loop. Mel had, in effect, used the binary representation of his own program as data, an act of optimization so deep it erased the line between code and machine.
The anecdote carries a wry moral about the cost of such brilliance. Mel’s code was magnificent and almost impossible for anyone else to maintain, and Nather recounts being asked to insert a feature, a deliberate delay so a customer could see the demo, that Mel quietly declined to make on the grounds that it was dishonest. The story honors Mel’s genius while acknowledging, gently, that his methods belonged to a vanishing world where one mind could hold an entire machine in its head.
“The Story of Mel” survived because it distilled a whole ethos into a single human portrait. Together with “Real Programmers Don’t Use Pascal,” it defined the archetype of the Real Programmer for later generations who would never touch a drum memory or hand-place an instruction. It is preserved in the Jargon File and recopied endlessly online, a primary text of hacker culture that turns a forgotten machine and a forgotten colleague into an enduring meditation on craft, obsession, and what is lost as tools grow kinder.