Rich Programmer Food

The thesis is the bluntest in Steve's catalogue: if you don't know how compilers work, you don't know how computers work. The title — credited to his brother Dave — turns on a line about the Olive Garden being where poor people go to eat rich people food, with most of a CS curriculum cast in the Olive Garden role. The dish Steve wants you to order instead is Compiler Construction, which he rates the second most important class in an undergraduate program. (The first, revealed in the last line, is Typing 101.) The argument is that compilers are the capstone that pulls a degree together — you can't understand one without machine architecture, OS, theory of computation, and language design all at once — and the problem they solve is everywhere. He lays out eight everyday situations (auto-formatting, doc extraction, syntax highlighting, refactoring a giant C++ codebase, talking to a proprietary router) and shows each is quietly a compilation problem, usually solved badly by someone reaching for a 2,500-line hand-rolled state machine because they never learned parsing. The cure is to learn the pipeline and then write one yourself, even a small interpreter.

Steve at his purest teacher — funny, profane, serious about the craft. The metaphor in the title is the lasting thing: rich programmer food is the deep, nourishing work, and learning compilers is how you graduate from "your little service APIs and JavaScript widgets" to it. The essay also contains one of Steve's most-quoted throwaway lines, the entirety of the section titled Large Systems Suck: "This rule is 100% transitive. If you build one, you suck."