THE READING ROOM / BOOK GUIDE
Revolution in the valley
Andy Hertzfeld, who wrote software for the original Macintosh, gathers first-hand accounts of how that computer was built, mixing engineering detail with the friction of a small group working under pressure.
About the book
Revolution in the Valley collects recollections from the people who built the first Macintosh at Apple in the early 1980s. Hertzfeld, a member of that team, draws on stories from engineers, designers and others close to the project, so the account moves between technical problems and the human ones around them. The book sits in the history of computing rather than in programming instruction, though readers who write software will recognize the constraints described.
The subject is the making of a product inside a company: decisions about hardware, interface and schedule, and the arguments those decisions caused. The recollections are short and specific, often anchored to a particular bug, prototype or disagreement. That structure suits a reader who wants texture more than a single authoritative narrative.
Apple's Macintosh Division and the wider computer industry of the period form the backdrop. Expect an insider's view, with the loyalties and blind spots that come with it.
How to read it
Approach the book as a collection of episodes rather than a continuous argument. The pieces vary in length and focus, and the interest lies in the accumulation of detail about how choices were made. Read for the engineering culture on display and for how individuals describe their own contributions.
The prose is plain and anecdotal, so the book moves quickly. Watch where accounts overlap or diverge; those moments show how memory and perspective shape a project history. Readers wanting a technical manual or a neutral corporate history should look elsewhere.
Who it suits
This suits readers curious about the early personal computer industry, software engineers interested in how small teams ship products, and anyone who enjoys first-hand workplace stories told by the people involved. It also gives designers and managers a concrete case of competing priorities inside a single project.
Reading considerations
The accounts come largely from participants, so the book carries an insider's perspective and should be read alongside more detached histories of the period. Treat the recollections as testimony rather than a complete record.
Follow the HN conversation
29 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.
