The origin stories for computing’s foundational vocabulary have been simplified in transmission — not falsified, mostly, but flattened. The memos and logbook entries behind them are stranger and more contingent than the versions that circulate. Each entry in this catalog covers one term: the story that travels, the document it traces back to, and the gap between them.

Bug

The standard account: Grace Hopper found a moth in a relay of the Harvard Mark II in September 1947, taped it into the logbook, and wrote “First actual case of bug being found.” Origin of the term.

The logbook entry contains its own refutation. Hopper wrote “actual” — using “bug” as established vocabulary, marking the moth as a specimen of an already-named category. The joke works because everyone in the room already knew the word. [3]

Thomas Edison used it in a March 1878 letter to William Orton, president of Western Union: “You were partly correct, I did find a ‘bug’ in my apparatus, but it was not in the telephone proper. It was of the genus ‘callbellum.’” [1] Eight months later, to Theodore Puskas: “‘Bug’ — as such little faults and difficulties are called — show themselves, and months of anxious watching, study, and labor are requisite before commercial success — or failure — is certainly reached.” [2]

Edison was using the term for telegraph malfunctions as early as 1876. [12] The word arrived in computing already in use, inherited from electrical engineering, present in the vocabulary before software existed.

Her logbook entry documents the word’s presence in the field. The moth was a prop for a joke in established vocabulary; the origin story is the joke, not the etymology.

Bit

The standard account: Shannon coined “bit” in “A Mathematical Theory of Communication,” 1948.

Shannon’s paper corrects this directly: “If the base 2 is used the resulting units may be called binary digits, or more briefly bits, a word suggested by J. W. Tukey.” [5] Tukey had coined the contraction in a Bell Laboratories memo dated January 9, 1947 — a year before Shannon’s paper appeared in the Bell System Technical Journal. [4]

The memo survives as a carbon copy in the papers of Herman Heine Goldstine, at the American Philosophical Society. [4] Not in Tukey’s own files. The originating document for one of computing’s foundational units is filed under a colleague’s name.

Shannon is why anyone knows the word. He used it in the most consequential paper in information theory, and it spread through that paper. But he said where he got it — in plain language, in the paper itself. The attribution has been there since 1948.

Byte

The standard account: “byte” is a natural shortening of “binary eight” or an obvious abbreviation for an 8-bit unit.

Werner Buchholz coined it for IBM’s Project Stretch in a memo dated June 11, 1956. [7] The spelling is a deliberate respelling of “bite,” chosen to prevent the word from being abbreviated to “b” — which would collide with the existing “b” for “bit.” [6, 7] The misspelling is engineering, not error.

At coinage, a byte was not eight bits. Stretch used variable-length bytes: anywhere from one to six bits depending on the instruction. The eight-bit byte was a subsequent decision; the earliest document in the Stretch archive supporting an 8-bit definition dates from September 19, 1956, three months after the term was coined. [7, 13] IBM System/360 in the mid-1960s settled the 8-bit byte as the industry standard.

The coinage and the current meaning arrived separately. “Byte” for “an 8-bit group” describes how the word is used now. It does not describe what the word meant when Buchholz wrote the June memo.

Software

The standard account: John Tukey coined “software” in 1958, in “The Teaching of Concrete Mathematics,” to describe programs as distinct from hardware.

Tukey’s 1958 usage is the first documented print use of the word to mean computer programs. The line, as traced by etymologist Fred Shapiro at Yale Law School: “Today the ‘software’ comprising the carefully planned interpretive routines, compilers, and other aspects of automative programming are at least as important to the modern electronic calculator as its ‘hardware’ of tubes, transistors, wires, tapes and the like.” [9]

But Richard R. Carhart had used “software” in print two years earlier, in the proceedings of a 1956 Institute of Radio Engineers symposium on quality control in electronics. [8] Secondary accounts consistently describe Carhart’s usage as referring to human personnel in a system, not to programs. Those proceedings are not available online, and Carhart’s exact text has not been confirmed from the primary source. The claim about what his usage meant stands as unverified.

If it holds: the word existed in 1956 with one meaning, and Tukey used it in 1958 with a different one. The computing world adopted Tukey’s sense. “Software” was repurposed, not coined, for what it came to mean.

A prior claim: Paul Niquette reports coining the word verbally in 1953. No contemporary record supports this; the account rests on his own memoir.

Daemon

The standard account: Unix daemons are named after Maxwell’s demon — the thermodynamics thought experiment.

The connection is real. But the version in circulation drops something.

Maxwell never used the word “demon.” In Theory of Heat (1871) and in his letters, he described “a being” or “a being who can play a game of skill with the molecules.” [10] The name came from William Thomson — Lord Kelvin — who introduced “daemon” in Nature in 1874. [15] Thomson chose the term in the Greek sense: not the religious demon but the classical daemon, a figure that operates in the background, unseen, performing work that no one has directed.

Fernando J. Corbató at MIT’s Project MAC introduced the word into computing around 1963. His account: “Our use of the word daemon was inspired by the Maxwell’s daemon of physics and thermodynamics… We fancifully began to use the word daemon to describe background processes which worked tirelessly to perform system chores.” [16] The analogy is precise. Maxwell’s being sorts molecules without being observed; a daemon handles system tasks without user direction. Both are background workers.

The DAEMON acronym — Disk And Execution MONitor — was invented after the name, as a post-hoc rationalization. [11, 16] Corbató’s team reached for the classical figure, not a hardware description.

Maxwell called it a being. Thomson named it. Corbató borrowed the name for something that worked the same way.