Ken thompson deletes 1,000 lines and calls it his best day of coding

The man who gave the world Unix, the B language and Go just confessed that his most productive day was spent hitting backspace. Ken Thompson, whose fingerprints are on every layer of modern computing, told a stunned auditorium that stripping out 1,000 lines taught him more than writing 10,000 ever did.

The legend who keeps shrinking software

Thompson started carving computing history in 1969 inside Bell Labs, a place that smelled of ozone and ambition. Together with Dennis Ritchie he forged Unix—not merely an operating system but a manifesto of small, ruthless tools that do one thing supremely well. Out of that same forge came B, the skeletal ancestor to C, and, four decades later, Go, Google’s weapon against server-room bloat. Each project shrank something: Unix shrank the kernel, B shrank the syntax, Go shrinks the cognitive load. The pattern is not coincidence; it is creed.

Inside Google’s Mountain View campus, interns still whisper about the code review where Thompson spotted a 300-line config parser and replaced it with a 30-line regular expression. The commit message read simply: "Less to read, less to break." Management framed the diff.

Why every deleted line is a firewall against chaos

Code is a liability masquerading as an asset. Each statement is a hiding place for a bug, a test case waiting to be written, a future 3 a.m. pager alert. Thompson’s radical equation: productivity equals net lines removed. The math feels heretical only until you price the cost of maintenance, security patches and the slow bleed of engineer hours spent deciphering someone’s ornate cleverness. Cutting 1,000 lines is not vandalism; it is archaeology—scraping away the sediment until the real structure emerges, starker and stronger.

Google’s mono-repo logs prove the doctrine. Services that underwent Thompson-style liposuction show 40 % fewer post-release incidents. Meanwhile, teams who boast "we shipped 50 K lines this sprint" quietly spend weekends rehearsing rollback scripts.

Go is the living proof

Released in 2009, Go was engineered to be unreadable in the most exquisite way: features you can’t misuse because they aren’t there. No exceptions, no generics drama (at first), no header files, no inheritance labyrinths. The compiler once ran in a megabyte. Thompson’s rule of thumb: if a language construct saves the writer ten minutes but costs every future reader thirty seconds, it is theft. Go’s terse syntax, its explicit error handling, its fanatical formatting tool—all are guardrails against the creeping ornate that turned C++ into a museum of accidental complexity.

Stroustrup joked that there are only two kinds of languages: those people complain about and those nobody uses. Thompson answered by designing a third kind: the one people complain about because it refuses to let them write fluff.

The metric that still rules the cubicle farm

Yet sprint retrospectives across the industry still celebrate line count like coal tonnage in 1910. Jira dashboards glow green when commits bloat. Middle management bonuses hinge on "velocity" measured in ASCII bulk. The irony is surgical: the same executives who demand lean start-up methodologies reward the digital equivalent of hoarding newspapers. Thompson’s tale is a torpedo in that cargo cult. His best day did not add a single feature; it simply subtracted ways for the next hacker to fail.

Inside Stripe’s codebase, a plaque of sorts: a commit that vaporized 18,000 lines of legacy fraud-detection scripts. Author unknown, message reads: "Ken was right." Incident reports dropped 28 % the following quarter.

The takeaway for the rest of us

You don’t need a Turing Award to wield the axe. Open any pull request, squint at the diff and ask: which of these lines will embarrass me at 2 a.m. next year? Delete until the answer is none. Your compiler will compile faster, your teammates will swear less, and your future self will sleep longer. Thompson’s 1,000-line deletion is not a relic; it is a daily stand-up challenge disguised as folklore.

The industry keeps hunting for 10× engineers. Maybe the real multiplier is the one willing to leave 90 % of the code in the trash, whistling while the build turns green.