
A Data General team races to design a 32-bit minicomputer in about a year.
Pulitzer-winning account of building a minicomputer against the clock
Kidder embedded with a Data General engineering team in 1978 and 1979 as they designed a thirty-two bit minicomputer, the Eagle, in about a year with a small team, few resources and no official sanction at the start. The book won the Pulitzer Prize and remains the standard account of what engineering work actually involves.
The organisational situation drives the narrative. Data General had committed its resources to a different project in North Carolina, and Tom West's team in Massachusetts built a competing machine in parallel, initially concealed. West recruited young engineers straight from university, gave them problems beyond their experience, and used what the team called signing up, meaning a voluntary commitment to unlimited hours in exchange for the responsibility.
Kidder describes the technical work accurately enough to be followed by a non-specialist, covering microcode, the debugging process, the logic analyser and the physical assembly. He also describes the psychological structure: the pinball metaphor in which winning means being allowed to play again, the deliberate withholding of information by West to preserve the team's sense of ownership, and the exhaustion and departures that followed the project's completion.
The book is a period document. Minicomputers no longer exist, and the specific technology is obsolete. The organisational pattern it describes, in which a small unofficial team outbuilds a resourced official one, recurs constantly. The treatment of motivation, in which the reward for shipping is the chance to do it again, describes something that most management literature does not capture. There are almost no women in the account, which reflects the industry at that time.
Anyone managing engineering teams who wants an honest account of what motivates technical work and what an intense project costs the people in it.
“I read The Soul of A New Machine as a senior in high school and, even though I don't include it in the reason I went to MIT, I'm sure it played a part.”
“Must-read for anyone in a product development or a startup environment.”
Chosen by shared topics, the entries that hold them, and the people who recommended both.
Computing as a run of collaborations, from Ada Lovelace and Babbage to Google.
Recommended by: Mohnish Pabrai, Patrick Collison, Bill Gates and 3 others
Three generations of hackers, from MIT's AI Lab to the Homebrew club and game makers.
Recommended by: Austen Allred, Ev Williams, Marc Andreessen and 3 others
Why well-run firms lose to cheaper, worse products that enter at the market's bottom.
“Clayton Christensen's big "aha" in Innovator's Dilemma is that eventually a product will become over-featured and as a result feature growth will slow, and along with it innovation.” — Bill Gurley
Source: Picture Proof of the Innovator’s Dilemma: SlideRocket
Recommended by: Bill Gurley, Drew Houston, Jim Collins and 29 others
Franklin's life as printer, scientist, diplomat and founder.
“…books I've recommended, highlighted to death, or forced on friends.” — Andrew Wilkinson
Source: Andrew Wilkinson's Bookshelf, neverenough.com
Recommended by: Alfred Lin, Andrew Wilkinson, Brad Feld and 11 others
How the stirrup and the plough reorganised medieval society and its economy.
Recommended by: Patrick Collison, Paul Graham
MIT's introductory computer science text, taught through Lisp and Scheme.
Recommended by: Bret Victor, Patrick Collison, Paul Graham and 1 other
As an Amazon Associate I earn from qualifying purchases.