"We tried to avoid, you know, records. We were told over and over that was probably the most serious mistake and the reason was the system would never catch on, because we didn't have records"
About this Quote
Paranoia and pragmatism collide in Thompson's almost offhand confession: they built something world-changing while actively trying to leave as little paper trail as possible. The little hedges - "you know", "probably" - are doing real work. They signal a scientist speaking from inside a culture where invention is informal, fast, and half-improvised, but also one where documentation is a kind of currency. "Records" here aren't just notes; they're legitimacy, reproducibility, and ultimately adoption.
The context is the early Unix era at Bell Labs, where Thompson (with Dennis Ritchie and others) was making a system that would outlive its corporate birthplace. The subtext is a classic tension in engineering: the joy of building versus the bureaucracy of proving. Their instinct to avoid records reads like an allergy to managerial oversight - or a desire to keep experimental freedom without inviting premature scrutiny. Yet the warning they kept hearing ("the system would never catch on") points to a deeper truth: technologies don't spread on elegance alone. They spread because other people can understand, trust, teach, and re-create them.
Thompson is admitting that "catching on" is a social process disguised as a technical one. A system becomes a standard when it has a story: manuals, design rationales, examples, and the breadcrumbs that let outsiders feel like insiders. The irony is sharp: the very hacker impulse that enabled Unix - move quickly, keep it light, stay unencumbered - also threatened to make it vanish into lab folklore. Documentation, boring as it sounds, is the bridge between a brilliant prototype and an ecosystem.
The context is the early Unix era at Bell Labs, where Thompson (with Dennis Ritchie and others) was making a system that would outlive its corporate birthplace. The subtext is a classic tension in engineering: the joy of building versus the bureaucracy of proving. Their instinct to avoid records reads like an allergy to managerial oversight - or a desire to keep experimental freedom without inviting premature scrutiny. Yet the warning they kept hearing ("the system would never catch on") points to a deeper truth: technologies don't spread on elegance alone. They spread because other people can understand, trust, teach, and re-create them.
Thompson is admitting that "catching on" is a social process disguised as a technical one. A system becomes a standard when it has a story: manuals, design rationales, examples, and the breadcrumbs that let outsiders feel like insiders. The irony is sharp: the very hacker impulse that enabled Unix - move quickly, keep it light, stay unencumbered - also threatened to make it vanish into lab folklore. Documentation, boring as it sounds, is the bridge between a brilliant prototype and an ecosystem.
Quote Details
| Topic | Coding & Programming |
|---|
More Quotes by Ken
Add to List



