Summary
Tracy Kidder's account of the engineers at Data General Corporation who designed a new minicomputer under enormous competitive pressure in the late 1970s won the Pulitzer Prize and the National Book Award in 1982 and effectively invented the genre of technology-company narrative journalism. Published in 1981, it remains the clearest account of what it actually feels like to make something new under deadline — and of what organizations do to, and with, people who care intensely about their work.
The book follows Tom West, a veteran Data General engineer, and the two teams he assembled — the Hardy Boys (experienced engineers) and the Microkids (recent college graduates) — who built the Eclipse MV/8000, a 32-bit minicomputer that Data General needed to compete with Digital Equipment Corporation's VAX. The project was officially invisible within Data General — a skunkworks operating below the company's official radar — which meant that the team had no formal resources and depended entirely on West's ability to protect them from organizational interference while also covertly obtaining what they needed.
Kidder embedded with the team for more than a year, and the resulting portrait is as much psychological as technical. The engineers he profiles — West himself, a complex man of suppressed intensity; Carl Alsing, the recruiter who built the team; Jonathan Raskin, a Microkid who signed on with little understanding of what he was committing to — are rendered as full people with inner lives, relationships, and private doubts. The work is rendered in sufficient technical detail to convey its difficulty without requiring the reader to be an engineer.
The book raises questions about organizational commitment and individual cost that remain relevant forty years later. The engineers worked hundred-hour weeks, sacrificed relationships and health, and received relatively modest compensation for their efforts. Many quit Data General shortly after the machine shipped. Kidder does not moralize about this; he describes it with precision and leaves the reader to draw conclusions. The "mushroom treatment" — keeping the team in the dark and feeding them manure — is his wry description of what West's management style required.
Talk to The Soul of a New Machine like its author wrote you back.
Get the ideas that fit your life — not generic summaries.
- Chat with the book
- Audiobook-style main ideas
- Adapts to your life and goals
- Helps you take action
Key takeaways
- 1.
Technical complexity can be made narratively compelling if the human stakes are made clear. Kidder's achievement was to find the human drama inside what looked like a purely technical project.
- 2.
Organizational dynamics can make or break a technical project. West's ability to protect his team from Data General's bureaucracy was as important as any engineering decision.
- 3.
The engineers signed on for reasons that weren't primarily financial. Pride, the desire to prove themselves, the satisfaction of solving hard problems — these were the real currencies.
- 4.
Burnout is the predictable consequence of sustained extreme commitment. Most of the team left Data General within months of shipping the product. The organization had taken what it needed.
- 5.
The soul of the machine is the people who built it — their beliefs, their compromises, their exhaustion, their satisfaction. Kidder's title is not metaphorical.
- 6.
The skunkworks model — hidden project, informal resources, intense team — is both more productive than formal development and more costly to the people in it.
- 7.
West's leadership style — ambiguous, demanding, strategically obtuse — worked because the team was smart enough to figure out what was actually wanted. It would not work universally.
- 8.
The competitive pressure in minicomputing in the late 1970s had a specific intensity that drove both innovation and organizational dysfunction. The market conditions made the human costs feel necessary.
Discussion questions
Use these on your own, with a book club, or as chat starters in Superbook.
- 1.
Kidder observes that the engineers worked extreme hours for relatively modest pay. What kept them doing it? Does the book fully explain the motivation?
- 2.
Tom West's management style — withholding information, strategically obscure — is effective in the book but would be described as problematic in a contemporary management context. How do you evaluate it?
- 3.
The young engineers — the Microkids — signed on without fully understanding what they were committing to. Is that a form of organizational manipulation?
- 4.
The machine was built and shipped. The team mostly quit. Does the project's success justify the human cost it required?
- 5.
The 'mushroom treatment' — keeping the team in the dark — is presented with dry humor. Is there a serious critique of organizational culture embedded in it?
- 6.
Kidder won the Pulitzer Prize for a book about engineers building a computer. What makes this material prize-worthy as literature?
- 7.
The book was published in 1981. How does the technology-company world it describes compare to the technology-company world of 2026?
- 8.
West is the book's central figure but remains somewhat opaque. Is that opacity a failure of the biography or a deliberate feature?
- 9.
The book is taught in engineering schools, business schools, and journalism programs. What does each of those disciplines take from it?
- 10.
The engineers find meaning in their work. Is that meaning sufficient compensation for what the organization takes from them?
- 11.
What does the book suggest about the relationship between organizational ambition and individual sacrifice?
Themes
Frequently asked questions
-
Do I need to know anything about computers to read The Soul of a New Machine?
No. Kidder explains the technical context clearly, and the engineering details are never the point. The book is primarily about people and organizations; the technology is the occasion.
-
Is the book dated given how much computing has changed?
The specific technology is dated, but the human dynamics — the organizational politics, the motivational structure, the costs of extreme commitment — are essentially timeless. It is regularly assigned in contemporary technology companies as a text about how teams work.
-
How long does it take to read?
About five to six hours. The book moves quickly despite its density. The short chapters and the narrative momentum carry most readers through in one or two sittings.
-
Is Data General still a company?
Data General was acquired by EMC Corporation in 1999. The minicomputer market it competed in was largely eclipsed by the personal computer revolution that began in the early 1980s.
-
Why did the Pulitzer committee honor a book about building a computer?
The prize was for general nonfiction, not technology writing specifically. The committee recognized Kidder's achievement in making the drama of technical work legible and emotionally engaging to general readers — a formal achievement as much as a reportorial one.
Similar books
Mountains Beyond Mountains
Tracy Kidder
The Right Stuff
Tom Wolfe
The Innovators: How a Group of Hackers, Geniuses, and Geeks Created the Digital Revolution
Walter Isaacson
