HackerTube.live
Books / Programming

THE READING ROOM / BOOK GUIDE

What the Dormouse Said

John Markoff

John Markoff traces how computing's counterculture and its military funders grew entangled in the same Bay Area decades, and how that history still shapes the machines on our desks.

About the book

What the Dormouse Said is John Markoff's history of the people and institutions that shaped personal computing in and around the San Francisco Bay Area during the 1960s. Its subject is the overlap between two worlds often told as opposites: the counterculture of experiment, altered consciousness and personal liberation, and the Cold War research economy that paid for much of the computing power those experiments ran on. Markoff, a longtime technology journalist, works through the engineers, researchers and institutions that sat at that intersection.

The book is organized around that tension rather than a single inventor or product. It follows how ideas about interactivity, augmentation of human thought and small machines moved between laboratories, campuses and communes. Markoff's interest is in how funding, ideology and personal conviction combined, and how the resulting culture of computing carried forward into the personal computer era. The title borrows from Jefferson Airplane, which signals the book's willingness to treat the 1960s as more than background scenery.

Readers should expect a work of reporting and synthesis rather than a technical manual. Markoff builds his account from interviews and archival work, and the narrative moves among many figures and sites. The payoff is a picture of computing history as messy and contingent, shaped by people whose politics and research agendas did not fit neatly into either corporate or academic categories.

How to read it

Approach the book as a cultural and institutional history first. Track the funding relationships and institutional affiliations as they recur, because those connections carry much of the argument. Markoff's prose is journalistic and accessible, but the cast is large and the chronology loops back on itself, so a reader who wants a clean timeline should keep notes on who is where and when.

Pay attention to how Markoff handles evidence. He draws on interviews with participants, which gives vivid detail but also means some recollections are contested or partial. The stronger passages connect individual choices to broader shifts in who could use computers and for what. Treat the book's claims about influence as arguments to weigh rather than settled findings, and notice where the narrative leans on personality and anecdote.

Who it suits

This suits readers curious about the cultural origins of personal computing, especially those who want more than a list of machines and dates. It will appeal to people interested in the 1960s Bay Area, in the relationship between government research and private experimentation, and in how technological optimism and political dissent can occupy the same room. Readers who enjoy narrative history with a large cast will find plenty to follow.

Reading considerations

The book is a journalistic synthesis, not a definitive academic account, and its emphasis on Bay Area figures leaves other regional and institutional stories in the background. Some participants' recollections are difficult to verify, so readers should treat vivid anecdotes as testimony rather than proof. The 2005 edition reflects the sources and debates of its time; check whether a later edition adds material before relying on it for current scholarship.

Follow the HN conversation

54 different recommenders are recorded in the upstream dataset. These are AI-classified source counts, not an independent rating.

Search HN comments about this book ↗

Explore videos on the same subject ↗

Book notes prepared with DeepSeek, using catalogue records and Open Library subject information. They are reading guidance, not a personal review or a verified chapter-by-chapter account. Book details can vary by edition. HN data methodology · Book metadata and covers.