Hacking Culture & The Cypherpunks
The Curious Kids Who Broke MIT's Computers (And Changed Everything)
The people who built the modern internet weren't following orders — they were breaking rules they thought were stupid.
The Idea
Before 'hacker' became synonymous with crime, it described something closer to a philosophy. At MIT's Tech Model Railroad Club in the late 1950s, a group of students began applying the word to their approach to systems — any system. A 'hack' was an elegant, unauthorised solution that revealed something true about how a thing worked. It was about understanding through intervention, not destruction. Steven Levy codified this into the Hacker Ethic in his 1984 book 'Hackers: Heroes of the Computer Revolution,' distilling what he'd observed across two decades of computing culture into a set of convictions. Chief among them: information should be free, access to computers should be unlimited, and authority — bureaucratic, institutional, technical — should be questioned whenever it obstructs learning. What made this ethic genuinely radical wasn't its anti-authoritarianism (that's common enough). It was the underlying belief that *hands-on engagement with a system is the only legitimate form of understanding*. You don't learn how a machine works by reading its manual. You take it apart. You stress-test it. You make it do something it wasn't supposed to do, and in that moment of breakage, you see its true structure. This is a different epistemology from the one most of us were schooled in. It's empirical, almost adversarial — and it produced, more or less directly, the open-source movement, the early internet, and the culture of tinkering that Silicon Valley still claims as its founding myth, even as it now builds the very walled gardens the original ethic despised.
In the World
Richard Stallman is the closest thing the hacker ethic has to a living saint — and his story shows both its power and its limits. In 1980, Stallman was a programmer at MIT's Artificial Intelligence Lab when a new Xerox printer arrived on the floor. It jammed constantly. Stallman knew that on the old printer, he could simply modify the software to alert users when paper jammed. He asked Xerox for the source code to do the same. They refused. The code was proprietary. This seemingly minor bureaucratic refusal became, for Stallman, a moral crisis. The hacker ethic held that restricting information was a kind of violence — not metaphorical violence, but a genuine obstruction of human flourishing and collective intelligence. He couldn't fix the printer. Nobody could. The knowledge was locked away, and they were all just supposed to tolerate it. In 1983, Stallman launched the GNU Project, and in 1985 published the GNU Manifesto — a document that reads less like a technical proposal and more like a philosophical tract on cooperation and freedom. His goal: build a completely free operating system, where 'free' meant freedom, not price. The word he reached for was *libre*. GNU's kernel work was eventually paired with Linus Torvalds' Linux in 1991, producing the operating system that now runs most of the world's servers, Android phones, and the majority of the internet's infrastructure. All of it traceable back to a jammed printer and a man who thought the refusal to share code was ethically indefensible.
Why It Matters
The hacker ethic isn't just computing history — it's a live argument about who gets to understand the systems that govern our lives. Most of us interact daily with software, platforms, and algorithms we cannot inspect, modify, or meaningfully question. We are users in the most passive sense of the word. What the original hacker ethic challenges is the assumption that this is fine — that complexity is a legitimate reason to hand over understanding to specialists and corporations. It insists that opacity in systems that affect people is a political problem, not just a technical inconvenience. You don't need to write code to take this seriously. The spirit of the ethic applies anywhere you find yourself accepting a system's outputs without examining its logic: why does this algorithm surface these results? Who decided these terms of service? What would happen if I pushed back here? The hackers of the 1950s and 60s were, at bottom, just deeply unwilling to be passive in the face of something interesting. That disposition — curious, probing, slightly irreverent — turns out to be one of the more useful things a person can cultivate.
A Question to Ponder
Which system in your daily life do you interact with but don't really understand — and have you ever genuinely tried to find out how it works?
Get a new one of these every morning.
Start learning with Thinkable