A People's History of Computing in the United States
Rankin deliberately begins her history of personal computing not in Silicon Valley garages but at Dartmouth College in the 1960s, where time-sharing systems gave ordinary students interactive access to mainframes for the first time.
She traces how educational networks, community computing projects, and time-sharing cooperatives created cultures of personal computing years before the microcomputer existed.
The book's central challenge is to the standard origin story: the idea that personal computing was born when hardware became cheap enough to own individually.
Rankin argues that the experience of personal computing — direct interaction, creative exploration, a sense of ownership over the machine — was a social achievement that emerged from institutional design decisions, not from miniaturization alone.
The result is a history that recovers forgotten networks like DTSS, PLATO, and the Minnesota Educational Computing Consortium and asks who gets to define what counts as the beginning.
Central argument
Rankin argues that personal computing was not born when microchips made hardware cheap enough to own individually, but was instead a social and institutional achievement that predates the microcomputer by over a decade. She recovers networks like DTSS at Dartmouth, PLATO, and the Minnesota Educational Computing Consortium to show that the defining qualities of personal computing — direct interaction, creative exploration, a felt sense of ownership over the machine — emerged from deliberate decisions about access, community structure, and educational design in the 1960s and 70s. The central thesis is that origin stories are political: defining personal computing as a hardware milestone erases the collective, often publicly funded, institutional work that made the experience possible first.
Critique
By centering educational and cooperative institutions, Rankin's account risks understating the material significance of commoditization — however culturally rich time-sharing communities were, their access remained contingent on institutional gatekeepers, and the microcomputer did genuinely decentralize that dependency in ways her framing can obscure. A thoughtful reader might press her on whether 'the experience of personal computing' and 'personal computing as a mass phenomenon' are being conflated: recovering precursors is not the same as showing that the Silicon Valley narrative is wrong about what actually scaled. The book is stronger as a corrective to triumphalism than as a complete alternative account of how computing became universal.
Why it matters for product
Rankin's core insight — that what users experience as 'theirs' is produced by institutional design choices, not just by the product itself — has direct implications for how CPOs think about platform ownership and community in digital products: the feeling of agency and belonging that drives retention is engineered through access models, permission structures, and community affordances, not delivered automatically by the interface. Her history of PLATO and time-sharing cooperatives also offers a concrete counterexample to the assumption that scale requires centralized control, which is a live question in decisions about ecosystem openness, developer platforms, and multi-tenant architecture. For product leaders, the deeper provocation is methodological: asking 'who defines what counts as the beginning' translates directly into challenging how teams frame discovery, whose problems are treated as the problem worth solving, and which user behaviors get counted as signal.