The internet's origins
The Nuclear Fear That Accidentally Wired the World
The internet was not invented to share cat videos or connect friends — it was designed to survive a nuclear attack.
The Idea
Most technologies get mythologised over time, but the internet's origin story is more interesting than the myth. The common version — that ARPANET was built to route communications around nuclear destruction — is actually a retroactive justification, not the founding intent. What ARPA (the Advanced Research Projects Agency, a US defence body) actually wanted in the early 1960s was something more mundane: a way to let expensive mainframe computers share resources across universities and research labs. Why have three machines sitting idle when one could serve many? The genuinely radical idea came from two independent thinkers working in parallel. Paul Baran at RAND Corporation and Donald Davies at the UK's National Physical Laboratory both arrived at the concept of 'packet switching' around the same time — breaking messages into small chunks, sending them by whatever route was available, and reassembling them at the destination. This was a profound departure from circuit switching, which dedicated a fixed line between two points for the duration of a call, the way telephone networks worked. Packet switching was resilient, efficient, and — crucially — it had no single point of failure. ARPANET launched in 1969, connecting four university nodes. The first attempted message was 'LOGIN.' The system crashed after the first two letters. So the internet's first transmitted word was, fittingly, 'LO' — a half-finished greeting that nonetheless reached across the country.
In the World
On the night of 29 October 1969, a UCLA student named Charley Kline sat at a Sigma 7 mainframe and tried to log into a computer at Stanford Research Institute roughly 560 kilometres away. His supervisor, Leonard Kleinrock, watched. Kline typed 'L' — Stanford received it. He typed 'O' — Stanford received it. He typed 'G' — and the system at Stanford crashed. Kleinrock called Stanford on a telephone to confirm what had come through. Two letters. The network had managed exactly that before falling over. By December 1969, the four-node ARPANET was stable and working. Within three years, email had been invented almost as an afterthought — Ray Tomlinson at BBN Technologies wrote the first email program in 1971, chose the @ symbol to separate user from machine, and later admitted he couldn't remember what the first message said because it seemed so insignificant at the time. What's striking about this early period is how little anyone understood what they were building. The engineers were solving specific, limited problems — resource sharing, robust communication between labs — not designing a global nervous system. Tim Berners-Lee's World Wide Web didn't arrive until 1989, and it was built on top of the internet infrastructure that already existed. The web is not the internet; it's one application running on it, the same way email or voice calls are. That distinction, routinely collapsed in everyday speech, hints at how poorly we understand the layered architecture of the thing we use every day.
Why It Matters
Understanding where the internet actually came from reframes how we think about technological change. It wasn't a vision that got executed — it was a series of small, practical problems that concatenated into something no one intended. The people building ARPANET were not dreaming of social media or e-commerce; they were trying to share processing time on expensive hardware. This pattern — technology built for narrow purposes transforming the world in ways its creators didn't foresee — repeats throughout history, but the internet is one of the cleanest examples. It should make us both more humble about predicting what current technologies will become and more attentive to the unglamorous infrastructure decisions being made right now in distributed computing, AI model deployment, and undersea cable networks. There's also something quietly important in remembering that the web is not the internet. The platforms you use daily — the ones that shape attention, politics, and culture — are a thin, commercially owned layer sitting on top of publicly funded research. The pipes are public; the buildings on top of them are private. That architectural fact has enormous consequences for how power is distributed in the digital world, and most people never think about it.
A Question to Ponder
If the internet was built without anyone intending to build the internet, what are we building today — without intending to — that will define the next fifty years?
Get a new one of these every morning.
Start learning with Thinkable