The moth in the logbook was a joke about a word already in use

Everything below about the origin of computer bugs comes from what actually happens rather than from what is supposed to.

The story as usually told

The account holds that a moth trapped in a relay caused a computer malfunction, and that this is why software faults are called bugs. The physical evidence exists, since the insect was taped into a logbook and the page has been preserved. The date and machine are documented, which makes this one of the better-attested anecdotes in computing history.

Everything in the story is true except the causal claim about the word, which is the part everyone repeats. It is a rare myth where the artefact is genuine and the conclusion drawn from it is not.

What the logbook actually says

The note accompanying the moth records it as the first actual case of a bug being found, which is a joke. The humour depends on the reader already knowing that bug means a fault, since otherwise there is nothing funny in it. A team inventing a term does not describe its first use as the first actual case of the thing.

The wording is therefore direct evidence against the origin story it is used to support. It is worth reading primary sources for exactly this reason, because they often contradict the summary attached to them.

The older engineering usage

Engineers used bug to mean a defect or difficulty in a system well before electronic computing existed. The usage appears in nineteenth-century correspondence about electrical and mechanical work, where it was already casual. It was common enough in technical contexts that dictionaries recorded it before the twentieth century was far advanced.

The term probably drew on a general sense of small hidden things causing trouble, though the precise route is uncertain. Telegraph and telephone engineering carried the word forward into the electrical industries that produced computing.

Why the moth story took over

It has a specific date, a named machine, a physical object and a photograph, which is far more than most etymologies offer. It also involves a famous and genuinely important figure in early computing, which gives it prominence.

A story with an artefact behind it feels settled, and few people go on to read the caption carefully. Museums display the page, which reinforces the association without necessarily endorsing the origin claim.

The anecdote is charming enough that correcting it feels ungenerous, which slows the correction down.

What is genuinely notable about it

The incident is a good illustration of what early computing hardware was like, with physical relays vulnerable to physical interference. It also documents a working culture that recorded such things with humour, which is historically interesting in itself. The team's decision to preserve the moth suggests they knew the joke was worth keeping.

None of this requires the etymological claim, and the anecdote is better without it. The real contribution of the figure involved lies in compiler design and programming languages rather than in an insect.

Printing a correction has a poor record of taking a myth out of circulation.

How technical jargon usually forms

Terms are borrowed from adjacent trades rather than invented, which is why so much computing vocabulary comes from telegraphy and manufacturing. Origin stories with a single dramatic moment are unusual and should be treated with suspicion by default. Words that appear suddenly with a documented birth, like the abbreviation for approval, are the exception rather than the rule.

Most vocabulary arrives gradually and its first uses are unremarkable, which is why they go unrecorded. A memorable origin story is often a sign that the actual history was too diffuse to remember.

The takeaway

The joke in the logbook is the evidence, and it has been quoted for eighty years by people who missed the punchline.

Believing it was ordinary. Continuing to is the avoidable part.