THE READING ROOM / BOOK GUIDE
The Soul of a New Machine
Tracy Kidder reports on a team at Data General racing to design a new minicomputer under deadline pressure, and on the engineers who gave their evenings and enthusiasm to the effort.
About the book
The Soul of a New Machine follows a group of engineers at Data General as they design a new minicomputer against a schedule set by corporate rivals. Kidder reports from inside the project, watching hardware and software take shape while managers above them weigh cost, risk and reputation. The machine is the occasion; the people doing the work are the subject.
Kidder writes about debugging sessions, design disagreements and the long hours a project of this kind demanded. He pays attention to how a small group organizes itself, how responsibility gets divided and how loyalty to a product forms among people who did not choose each other.
The result is a portrait of engineering as a social activity. Decisions about architecture and testing arrive alongside arguments about who owns a problem and who gets credit for solving it. Kidder keeps the technical material legible for readers outside the field while staying close enough to the work to show why it was difficult.
How to read it
Approach the book as reporting rather than a technical manual. Kidder explains enough about minicomputers to make the team's choices intelligible, but the interest lies in how people behave under a deadline. Follow the named engineers and managers as characters; their shifting alliances carry much of the narrative.
The prose is direct and the scenes are concrete, so the book moves quickly for its length. Readers who want a tidy account of how a computer is built may find the emphasis on personality and company politics unexpected. Those details are the point, and they reward a slower reading of the meetings and late-night problem solving.
Who it suits
Readers curious about how software and hardware teams actually work will find a grounded account of engineering life, including the unglamorous parts. Managers who want to understand project pressure and team dynamics will recognize the tensions Kidder describes. Anyone interested in the history of computing in the late 1970s and early 1980s gets a close view of one company's effort to stay competitive.
Reading considerations
The book is a period piece. Its workplace culture, company structures and technology belong to the late 1970s, so readers should not treat it as a guide to current practice. Kidder's access came through the team he followed, which shapes whose perspective dominates; keep that in mind when weighing claims about management and motivation.
Follow the HN conversation
260 different recommenders are recorded in the upstream dataset. These are AI-classified source counts, not an independent rating.
Read mtVessel’s original comment (2019-02-08) ↗
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.
