When we talk about the history of the internet, names like Vint Cerf, Bob Kahn or Tim Berners‑Lee usually come first. Hidden one step earlier in the timeline is a quieter, but foundational figure: Joseph Carl Robnett Licklider, better known as J.C.R. Licklider.
Who was Licklider?
Born in 1915 in Missouri, Licklider originally studied psychology and physiology, not electrical engineering. He was fascinated by how humans perceive sound and information. This interest slowly pulled him toward early computers, which at the time were room‑sized, batch‑processing machines.
While many saw computers as glorified calculators, Licklider saw them as interactive partners. During the 1950s he worked at MIT and later at Bolt Beranek and Newman (BBN), focusing on human–computer interaction and time‑sharing systems. The key idea: instead of one user booking the whole machine for hours, many users could work interactively through terminals.
A black and white portrait photograph of J.C.R. Licklider. — Image: Unknown author Unknown author / Wikimedia Commons, Public domain
The key contribution: imagining a global computer network
In 1962, Licklider became head of the Information Processing Techniques Office (IPTO) at ARPA, the research agency of the U.S. Department of Defense that would later be called DARPA. From this position, he started pushing a radical idea: a world‑wide network of computers.
In a series of internal memos, he described something he jokingly called the “Intergalactic Computer Network.” The name was playful, but the concept was serious and surprisingly modern:
- geographically distributed computers connected into one network;
- users able to access data and programs from any node, not just their local machine;
- the network as a medium for communication and collaboration, not just file transfer.
He imagined scientists sharing code, documents and processing power across that network — decades before email, FTP or the web became reality. At a time when computers were rare, isolated and incredibly expensive, this was closer to science‑fiction than engineering.
The invisible architect behind ARPANET
Licklider did not design the ARPANET protocols himself. Others, like Larry Roberts, Leonard Kleinrock and Paul Baran, worked out the details of packet switching and routing. But Licklider laid the intellectual and organizational groundwork that made ARPANET possible.
As IPTO director he:
- funded key projects in time‑sharing and networking at MIT, UCLA, Stanford and other labs;
- insisted that ARPA‑funded computers be connected, not isolated islands;
- encouraged researchers to think in terms of a shared network community.
In an early memo to his colleagues, he talked about the need to build a community of people "who are already using computers and will want to communicate through the network." In other words, he was thinking not just about cables and protocols, but about users and how they would collaborate.
Logical network map of ARPANET from March 1977 showing connected host nodes and IMPs. — Image: ARPANET / Wikimedia Commons, Public domain
By the late 1960s, when ARPANET's first nodes went online and packet switching proved itself, many of the engineers involved acknowledged Licklider’s early vision as a key inspiration. He had left ARPA by then, but the project still followed the trajectory he had set.
Little‑known fact: a psychologist shaping computing
One of the most interesting aspects of Licklider’s story is that he remained, at heart, a psychologist. In 1960 he published the influential paper "Man‑Computer Symbiosis", where he argued that humans and computers should complement each other:
- humans: goals, intuition, creativity;
- computers: speed, accuracy, data handling.
This way of thinking shaped everything from time‑sharing systems to modern IDEs, search engines and voice assistants. For embedded and electronics people, it’s a reminder that user experience is not an afterthought; it is a design axis, just like power, cost or clock speed.
Why young engineers and makers should care
If you are building an IoT node on ESP32, a sensor gateway on STM32, or a home server on Raspberry Pi, you’re living inside Licklider’s dream. Your devices are small, cheap and powerful — very different from 1960s mainframes — but the core idea is exactly what he described: people and computers, collaborating over a network.
There are a few lessons from Licklider’s career that are especially relevant for today’s embedded community:
- The biggest innovations often start as questions, not answers: "What if anyone could access any information from anywhere?"
- Don’t treat hardware and software as isolated; design around how humans will interact with your system.
- You don’t have to invent a new transistor to change the world; sometimes funding, connecting and inspiring the right people is the real leverage.
- Networking is a feature, not an add‑on. Many of the most impactful projects today are about how devices talk to each other, not just how fast they run a loop.
The next time you open a serial monitor, push firmware over the air, or spin up a tiny web server on your microcontroller, remember that someone in 1962 already imagined a planet‑scale web of interactive computers. J.C.R. Licklider never saw Wi‑Fi or smartphones — but he helped make a world where your latest prototype can instantly talk to any other device on Earth.
