Museum Wire
Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆
Keyboard Navigation
W↑
A←
S↓
D→
or arrow keys · M for map · Q to exit
← Back to Hall of Heroes
ENIAC pixel portrait
⬡ Pioneerfame

ENIAC

Electronic Numerical Integrator and Computer

The First Computer That Wasn't a Room Full of People

forties_fifties · 3 min read · Decommissioned
“It is easier to change the specification to fit the program than vice versa.”

The Machine

ENIAC — Electronic Numerical Integrator and Computer — was completed in February 1946 at the University of Pennsylvania, funded by the U.S. Army to compute artillery firing tables. It was 100 feet long, 10 feet tall, and contained 17,468 vacuum tubes, 7,200 crystal diodes, 1,500 relays, and 70,000 resistors. It weighed 30 tons and occupied 1,800 square feet.

It computed 5,000 additions per second. For context: your laptop completes roughly 100 billion additions per second. ENIAC was one-twenty-billion'th as fast as the device you might be reading this on.

It was, at the time, the most powerful computational device in human history.

Programming ENIAC

Programming ENIAC was physical. The machine's operations were configured via patch panels — physical cables plugged into a board, routing signals between components. A "program" for ENIAC was a wiring diagram. Changing programs meant physically rewiring the machine. It took days.

The women who programmed ENIAC — Kay McNulty, Betty Jennings, Betty Snyder, Marlyn Meltzer, Fran Bilas, and Ruth Lichterman — are an exhibit in the museum's unwritten section on invisible labor. They were initially referred to as "computers" (the human job title that preceded the machine) and were not invited to the ENIAC dinner celebrating the machine's unveiling.

The Bug

The term "bug" in computing traces to the ENIAC era, though the specific incident is usually attributed to Grace Hopper and the Harvard Mark II in 1947 — a moth found physically trapped in a relay, causing a program failure. The relay was logged as a relay failure. The cause: "First actual case of bug being found." The moth was taped into the logbook.

ENIAC's vacuum tube failures were so frequent that the engineering challenge was not making the tubes reliable — it was writing programs that could complete before a tube failed. Reliability engineering in the ENIAC era meant racing the hardware clock.

Why It Belongs Here

ENIAC is the root node of every exhibit in this museum. Every pattern documented here — every concatenated query, every greedy initializer, every runaway migration — is a descendant of the problems ENIAC's programmers first encountered: how do you write instructions that run correctly on hardware that fails? How do you test a program when "running the test" takes hours of physical configuration? How do you debug when the bug might be a literal insect?

The answers those programmers found — documentation, testing procedures, modular thinking, systematic verification — became software engineering. Before ENIAC, programming was mathematics. After ENIAC, programming was engineering .

30 tons. 150 kilowatts. 5,000 additions per second. The first computer was also the first computer that was too slow, too large, and too unreliable. That hasn't changed. Only the scale has.