"If a listener nods his head when you're explaining your program, wake him up"
About this Quote
Nodding is supposed to mean understanding; Perlis treats it as a warning light. In this one-liner, he flips a common social cue into an indictment of how programmers talk about their work - and how listeners perform comprehension to keep the conversation moving. The joke lands because anyone who has sat through a technical explanation knows the nod: polite, rhythmic, and often completely detached from the actual content. Perlis is saying that if your audience can "agree" with you while you're describing your program, you're probably not describing the real program at all.
The intent is partly pedagogical, partly adversarial. Perlis is pushing against the seduction of smooth narratives in computing: the tidy, linear explanation that makes a messy system sound obvious. Real software is full of edge cases, trade-offs, and implicit assumptions. If those aren't surfacing, the listener isn't tracking - or you're sanding down the complexity to the point of dishonesty.
Context matters: Perlis helped define early computer science as a discipline, when "programming" was shifting from clever hacks to a form of engineering with rigor, languages, and abstractions. His aphorism is a defense of precision. "Wake him up" isn't about rudeness; it's about forcing contact with the difficult parts: ask for predictions, run through a counterexample, expose the invariants. Understanding in software is active, not ceremonial. If it's too easy to nod along, someone is sleepwalking into production.
The intent is partly pedagogical, partly adversarial. Perlis is pushing against the seduction of smooth narratives in computing: the tidy, linear explanation that makes a messy system sound obvious. Real software is full of edge cases, trade-offs, and implicit assumptions. If those aren't surfacing, the listener isn't tracking - or you're sanding down the complexity to the point of dishonesty.
Context matters: Perlis helped define early computer science as a discipline, when "programming" was shifting from clever hacks to a form of engineering with rigor, languages, and abstractions. His aphorism is a defense of precision. "Wake him up" isn't about rudeness; it's about forcing contact with the difficult parts: ask for predictions, run through a counterexample, expose the invariants. Understanding in software is active, not ceremonial. If it's too easy to nod along, someone is sleepwalking into production.
Quote Details
| Topic | Coding & Programming |
|---|
More Quotes by Alan
Add to List






