“Given enough eyeballs, all bugs are shallow.”
Eric S. Raymond offered this line in his essay “The Cathedral and the Bazaar”. Raymond described the Linux development model and argued that a broad group of beta testers and contributors increases the chance that a problem will be recognized and understood by someone whose experience fits it. He named the observation Linus’s Law. Keeping the original occasion in view protects the quote from being stretched beyond its evidence.
Review diversity can change the difficulty of a defect. What is mysterious to one maintainer may be familiar to another, and rapid feedback makes it more likely that characterization and repair happen before the problem becomes entrenched. The sentence becomes concrete when it is connected to interfaces, incentives, and observable results. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
More observers do not help automatically. People need access, motivation, relevant skill, reproducible reports, and maintainers able to evaluate changes. Security-sensitive work may also require coordinated disclosure rather than immediate publicity. The quotation remains useful only when its memorable wording does not erase evidence that points in another direction. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Open repositories, bug bounties, and public standards embody the same possibility, but participation must be supported. Raymond’s maxim is strongest when projects reduce reporting friction, credit investigators, and turn many observations into disciplined decisions. That makes the quotation a tool for present decisions while respecting the limits of the original claim. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Eric S. Raymond offered this line in his essay “The Cathedral and the Bazaar”. Raymond described the Linux development model and argued that a broad group of beta testers and contributors increases the chance that a problem will be recognized and understood by someone whose experience fits it. He named the observation Linus’s Law. Keeping the original occasion in view protects the quote from being stretched beyond its evidence.
The source record connects the wording to his essay “The Cathedral and the Bazaar”, which is the context used for this post.
Review diversity can change the difficulty of a defect. What is mysterious to one maintainer may be familiar to another, and rapid feedback makes it more likely that characterization and repair happen before the problem becomes entrenched. The sentence becomes concrete when it is connected to interfaces, incentives, and observable results. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
More observers do not help automatically. People need access, motivation, relevant skill, reproducible reports, and maintainers able to evaluate changes. Security-sensitive work may also require coordinated disclosure rather than immediate publicity. The quotation remains useful only when its memorable wording does not erase evidence that points in another direction. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Open repositories, bug bounties, and public standards embody the same possibility, but participation must be supported. Raymond’s maxim is strongest when projects reduce reporting friction, credit investigators, and turn many observations into disciplined decisions. That makes the quotation a tool for present decisions while respecting the limits of the original claim. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.