“Real Programmers Don’t Use Pascal” is a satirical essay by Ed Post, published as a letter to the editor of Datamation in its July 1983 issue (volume 29, number 7). It was written as a parody of the contemporary best-seller “Real Men Don’t Eat Quiche,” transplanting that book’s mock-macho posturing into the world of computing. The piece quickly escaped its original magazine and became one of the most widely copied texts in programming folklore, circulated for decades on Usenet, mailing lists, and personal home pages.
The essay draws a sharp line between two kinds of programmer. On one side stands the Real Programmer, who “writes in Fortran” and, when Fortran will not do, drops into assembly language. On the other side are the “Quiche Eaters,” the soft, university-trained adherents of structured programming who favor Pascal, abhor the GOTO statement, and worry about readability and maintainability. The whole joke runs on inverting the values that the structured-programming movement had spent the 1970s promoting, treating discipline and abstraction as signs of weakness rather than progress.
Post’s Real Programmer is a recognizable type rendered in caricature. He does not use interactive debuggers because he can read core dumps in his head; he does not comment his code, on the grounds that if it was hard to write it should be hard to understand; and he treats any language feature that protects the programmer from himself as an insult. The text catalogues the Real Programmer’s tools, his disdain for “user-friendly” software, and his preference for hardware close enough to the metal that the distinction between code and machine nearly vanishes.
The essay is best read alongside “The Story of Mel,” Ed Nather’s Usenet tale from the same year. Nather opens by quoting the very claim Post had popularized, that “Real Programmers write in FORTRAN,” and then offers Mel as a real-life embodiment of the archetype. Together the two texts fixed the figure of the Real Programmer in the culture: a half-mythical wizard who works closer to the machine than anyone should, whose skill is undeniable and whose methods are indefensible.
What gives the satire its staying power is that it cuts both ways. It mocks the macho coder who refuses every modern convenience, but it also needles the structured-programming establishment whose evangelism could be just as smug. The essay survives as a primary artifact of how programmers of the early 1980s argued about their own craft, captured in a tone of affectionate ridicule that the field has returned to again and again, from editor wars to language flame wars.