The Servant Problem, Revisited
John Kemeny wrote this book in 1972 with the calm confidence of a man who had already built something that worked. He had co-invented BASIC, helped design the Dartmouth Time-Sharing System, and watched undergraduates — English majors, not engineers — sit down at terminals and write programs that ran. From that experience he extrapolated a future of home terminals, national computer networks, personalized news delivery, automated libraries, and a citizenry fluent in computational thinking. He framed the whole enterprise as symbiosis: two species, human and machine, each contributing what the other lacked. Speed and memory on one side. Judgment, intuition, and pattern recognition on the other. The metaphor is biological, deliberate, and — he would insist — not merely metaphorical. He spends real pages arguing that computers might qualify as a new species, that self-reproducing robots could initiate their own evolutionary line. In 1972 this was speculative but disciplined. In 2026 it reads like the first draft of a conversation we are now having in earnest, though with rather different vocabulary.
The prescience is remarkable in its specifics. Kemeny describes a system where reporters file stories into a computer, editors tag them by subject and priority, and readers at home terminals select what they want to read at whatever depth they choose — essentially RSS feeds, news apps, and algorithmic curation, minus the algorithm. He envisions computerized credit transactions replacing cash, inventory lookups from home, personalized education through interactive terminals, and a national reference library where users refine searches through iterative keyword dialogue with the machine. That last one is not a metaphor for Google Scholar; it is Google Scholar, plus the conversational refinement loop that now characterizes interactions with large language models. He predicted that computer communication traffic would eventually exceed telephone traffic. He was right, and the margin is absurd. His proposed network of seven regional computing centers serving eighty cities is structurally closer to cloud computing's geography than he could have known — though Amazon Web Services has rather more than seven.
What Kemeny could not see is what almost no one in 1972 could see: that the economics of attention would matter more than the economics of access. His entire framework assumes that the bottleneck is getting humans and computers into the same room, and that once you solve the access problem — cheap terminals, good networks, simple languages — the symbiosis naturally follows. He never imagines that people might have unlimited access to computation and use it primarily to argue with strangers, watch short videos, or generate slop. His citizens are earnest. They read their personalized newspapers carefully. They use home terminals to check store inventories and study calculus. The possibility that the computer might become the dominant partner in the relationship, shaping human attention rather than serving human intention, does not appear. Nor does surveillance capitalism, platform monopoly, or the weaponization of the very data-sharing he advocates. His chapter on privacy concerns is thoughtful but ultimately trusting: he believes oversight panels and good policy will handle it. The NSA, Facebook, and Clearview AI were not in his models. His blind spot is not technological but political — he assumes institutions will remain accountable as they become more powerful, a faith characteristic of midcentury American liberalism and the Ivy League presidency he would later hold.
The deepest resonance now is in his insistence on the division of labor. Kemeny is emphatic: computers are fast, obedient, and stupid. Humans are slow, unreliable, and brilliant. The partnership works because each compensates for the other's deficiencies. He warns against trying to make computers replicate human talents like pattern recognition, language understanding, and associative memory, calling such efforts wasteful given 1960s results. He was right about the waste — for fifty years. Then he was wrong. The emergence of large language models and neural networks has collapsed exactly the distinction he built his framework on. Computers now do pattern recognition, translation, and associative memory at scale. The servant has acquired some of the master's talents, and the question of who guides whom has become genuinely unsettled. His book is not invalidated by this — it is deepened. The symbiosis he described assumed a stable complementarity. What happens when the complement starts to overlap?
Kemeny's book sits at a hinge point between the heroic engineering narratives of the 1950s and the networked-society speculation of the 1980s and 1990s. He draws from von Neumann, Turing, Licklider's "Man-Computer Symbiosis," and Forrester's systems dynamics work, and he feeds forward into the visions of Negroponte, Kay, and eventually Berners-Lee. BASIC itself — his most lasting practical contribution — democratized programming in exactly the way he hoped, then was largely abandoned by professionals while persisting as a pedagogical ghost. The book's real legacy is not any single prediction but its governing assumption: that the relationship between humans and computers is the unit of analysis, not the computer alone. That idea is now so pervasive it is invisible, which is the surest sign of influence. But here is what the book now asks that it did not ask in 1972: if the computer can learn, associate, recognize, and even generate — if it is no longer the obedient servant Kemeny described — then what exactly is the human's contribution to the symbiosis, and how do we know when we are no longer needed?