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 BelongingLaw 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 FlagLaw 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 DistributionAXM-002Boolean & Propositional Logic — True, False, and the Excluded MiddleLaw 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 Outage2025Operation Chrysalis: The Notepad++ Supply Chain Hijack2025Replit Agent — The Vibe Code Wipe2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem2024Air Canada Chatbot — The Policy That Wasn't2024Change Healthcare — One-Third of US Healthcare, One Missing MFA2024CrowdStrike — The Security Update That Broke the World2024Google Gemini Image Generation — The Six-Day Pause2024XZ Utils — The Two-Year Infiltration20233CX — The Supply Chain That Ate Another Supply Chain2023Amazon Prime Video — The Per-Frame State Machine2023Bing Sydney — The Chatbot That Went Rogue2023Samsung ChatGPT Leak — The Employee Who Pasted the SecretEFFODE · LEGE · INTELLEGELaw 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 BelongingLaw 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 FlagLaw 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 DistributionAXM-002Boolean & Propositional Logic — True, False, and the Excluded MiddleLaw 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 Outage2025Operation Chrysalis: The Notepad++ Supply Chain Hijack2025Replit Agent — The Vibe Code Wipe2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem2024Air Canada Chatbot — The Policy That Wasn't2024Change Healthcare — One-Third of US Healthcare, One Missing MFA2024CrowdStrike — The Security Update That Broke the World2024Google Gemini Image Generation — The Six-Day Pause2024XZ Utils — The Two-Year Infiltration20233CX — The Supply Chain That Ate Another Supply Chain2023Amazon Prime Video — The Per-Frame State Machine2023Bing Sydney — The Chatbot That Went Rogue2023Samsung ChatGPT Leak — The Employee Who Pasted the SecretEFFODE · LEGE · INTELLEGE
Keyboard Navigation
W
A
S
D
or arrow keys · M for map · Q to exit
← Back to Hall of Heroes
Thomas E. Kurtz pixel portrait
⬡ Pioneer⬢ Builderfame

Thomas E. Kurtz

@kurtz

Co-creator of BASIC

1960s · 3 min read · Decommissioned
We were thinking of the students. BASIC was designed for a broad audience, not for computer professionals.

The Story

In the spring of 1964, at 4:00 AM on May 1st, two programs written in a new language called BASIC ran simultaneously on a General Electric GE-225 at Dartmouth College. Thomas Kurtz and John Kemeny had just proved their thesis: programming didn't have to be the exclusive domain of specialists.

The context matters. In the early 1960s, writing a program meant punching cards, submitting a batch job, and waiting hours or days for output. FORTRAN and COBOL existed but demanded expertise. Kurtz and Kemeny — both mathematicians, not computer scientists — believed that computing was too important to remain behind that barrier.

BASIC (Beginner's All-purpose Symbolic Instruction Code) was deliberately simple. Line numbers. GOTO. PRINT. INPUT. No data types to declare, no memory to manage, no compilation step to wait for. You typed a program, typed RUN, and something happened immediately. The Dartmouth Time-Sharing System let dozens of students use the same computer simultaneously, each getting an interactive session.

The design made trade-offs that purists hated. No structured programming. No scoping. Global everything. GOTO as the primary flow control. These weren't oversights — they were decisions. Kurtz and Kemeny understood that a language requiring knowledge of structured programming before you could print "HELLO WORLD" wasn't a language for beginners. They chose accessibility over structure, knowing the cost.

BASIC spread everywhere. It was ported to minicomputers, embedded in ROM on early microcomputers, and became the first programming language for an entire generation. The Apple II, the Commodore 64, the TRS-80 — they all booted to a BASIC prompt. Bill Gates and Paul Allen wrote Altair BASIC in 1975, and Microsoft was born.

The lineage runs through decades. BASIC begat GW-BASIC, which begat QBasic, which begat Visual Basic, which begat VBA and VB.NET. Each generation added structure — subroutines, then functions, then objects, then proper scoping — but the DNA of accessibility persisted.

Thomas Kurtz continued working on BASIC for decades, developing True BASIC in the 1980s — an attempt to modernize the language with structured programming while preserving its approachability. He died in November 2024, sixty years after that first 4 AM run.

Why They're in the Hall

Kurtz is a Pioneer and Builder whose impact is measured not in technical sophistication but in reach.

Pioneer: Before BASIC, programming was a priesthood. After BASIC, it was something a 12-year-old could do on a Saturday morning. That transition — from expert craft to accessible skill — is the most consequential shift in computing history. Every "learn to code" initiative, every drag-and-drop programming environment, every low-code platform owes a debt to the principle Kurtz and Kemeny established: programming should be for everyone.

Builder: The language itself is the artifact. It shipped on millions of machines. It was the first code millions of people ever wrote. The VB6 developers whose initialization patterns populate the Greedy Initializer exhibit — they trace their lineage through BASIC. The language that taught them to program shaped how they thought about programming, for better and for worse.

The trade-off Kurtz made — accessibility over structure — is the kind of deliberate design decision that TechnicalDepth exists to examine. GOTO wasn't a mistake. Global state wasn't ignorance. They were choices made for a specific audience, with consequences that played out over generations. BASIC taught a generation to program. It also taught them patterns they'd spend the next generation unlearning. Both of those outcomes were real, and neither invalidates the other.