Revolution in the Valley
Source: https://www.folklore.org/ ↗
Hertzfeld was a core member of the original Macintosh team and wrote these anecdotes first as entries on folklore.org, a wiki he built to collect first-hand accounts from the people who were there.
The stories cover 1979 to 1984 and capture the daily texture of building a product under extreme pressure with a small team that believed it was changing the world.
What makes the book valuable beyond nostalgia is its granularity — Hertzfeld describes specific technical decisions, specific arguments about resource constraints, and specific moments where craft and compromise met.
The folklore.org site remains freely accessible and contains material not included in the printed edition.
It is one of the few primary-source accounts of product development from inside a team that actually shipped something that mattered.
Central argument
Hertzfeld does not argue a thesis in the conventional sense — instead, he makes a cumulative case through granular anecdote: that the Macintosh was built not through process or methodology but through a specific convergence of obsessive craft, resource scarcity, interpersonal intensity, and shared belief in consequence. The implicit argument is that product quality at that level is inseparable from cultural conditions that are difficult to engineer deliberately. The book shows, story by story, that the decisions which defined the Mac — technical trade-offs, interface choices, deadline compromises — were made by individuals under pressure, not by systems.
Critique
The primary limitation is one of selection and memory: these are accounts written years after the fact by someone who was both participant and archivist, which means the record is shaped by what Hertzfeld found worth preserving and how those events felt in retrospect. The folklore.org format encourages vivid episodes over structural analysis, so the book reveals almost nothing about what failed, what was discarded, or what the team got wrong and corrected — the parts of product development that are often most instructive. There is also no serious reckoning with the human cost of the culture Hertzfeld describes with evident admiration.
Why it matters for product
For a CPO, the book is most useful not as a model to replicate but as a benchmark for what it actually feels like when a small team internalises product quality as a non-negotiable — Hertzfeld's specificity about resource constraints and craft arguments gives concrete texture to the abstract idea of a high-ownership team. The tension the book surfaces between creative intensity and sustainable organisation is directly relevant to decisions about team size, autonomy, and how much pressure a product culture can carry before it becomes extractive rather than generative.