Philip Moorby, 2016

“People value your product based on the quality of the bugs they find.”

Moorby offered a wry engineering observation shaped by creating Verilog and tools used to describe and verify complex digital hardware. Reading Philip Moorby in the setting of “Computer History Museum Fellow Profile” changes how the quotation lands. The year 2016 identifies the documented source, while August 22 is only this series calendar position. Returning to the original work verifies authorship, clarifies the problem under discussion, and marks where modern interpretation begins.

Users judge reliability not only by whether defects exist, but by how predictable, understandable, and recoverable they are. For a present-day team, the idea becomes useful when it changes a decision instead of decorating a slide. A reviewer can apply it to an interface, architecture, dataset, workflow, classroom, or governance rule, naming the desired outcome and the evidence that could challenge a preferred story.

A charming bug is still a defect; safety-critical systems require rigorous prevention, detection, and response. This qualification keeps the sentence from becoming a universal slogan. Technical results live inside organizations, markets, laws, and communities, where a narrow benchmark rarely settles the whole question. Responsible use makes assumptions visible, records tradeoffs, and asks who gains convenience and who inherits risk.

Toolchains, compilers, and AI systems earn trust through transparent failure modes and strong debugging support. The quotation endures as a method rather than a formula: understand the source, test the claim in its new environment, disclose important limits, and revise the implementation when real conditions disagree. What matters is whether the idea helps make technology more understandable, dependable, useful, and answerable to the people it affects.