Library Discover Ideas My library Paths Compare Shelves Collections Method
The Soul of a New MachineTracy KidderCover of The Soul of a New Machine by Tracy Kidder
Two sources agreed 3 min read

Technology & AI

The Soul of a New Machine

Tracy Kidder

Tracy Kidder's Pulitzer-winning account of a team at Data General building a minicomputer against a deadline in 1980 — the book that established what technology narrative journalism could be.

First published
1981
Publisher
Little, Brown and Company
Pages
293
Level
Entry
ISBN-13
9780713914825
computingnarrativehistory

Record checked against

Catalogue note

Reads as
TechnicalAssumes and builds craft knowledge.
Level
Accessible / FoundationalNo prior reading assumed.
Approach
Applied
Written for
Engineers, Newcomers to the subject
Your shelf

Saved in this browser only — no account, nothing sent anywhere. My library

Read this if

  • You build software and want the ideas under the tools.
  • You read for the writing as much as for the argument.
  • You want to know how we got here.
  • You work in this area and want depth rather than an overview.
  • You are starting from scratch here and want a way in that assumes no prior reading.
01

What it is about

A group of engineers, many of them recent graduates, building a 32-bit minicomputer in roughly a year, under a manager who has committed to a schedule nobody believes.

The machine matters less than the people. Kidder embedded with the team for the duration and wrote about what building something difficult does to the people doing it.

The machine is the occasion. The subject is what building something hard does to the people building it.

Devmark’s reading — not a quotation from the book
02

Signing up

The book's central concept and its most enduring contribution to the vocabulary of technical work. Engineers were recruited by being offered a difficult problem and near-total autonomy, and in accepting they signed up — committing to whatever hours the work required, without being asked directly.

Kidder is clear-eyed that this was a deliberate management technique, and that the engineers largely knew it and accepted anyway.

03

The Hardy Boys and the Microkids

The two sub-teams: the hardware engineers and the younger engineers writing microcode, working in parallel on a machine that had to work as one thing.

The interfaces between them, and the arguments at those interfaces, are the book's best organisational material — and describe a dynamic that anyone who has shipped a technical product will recognise immediately.

04

Tom West

The project's manager, and one of the more complicated figures in technology writing. He is manipulative, evasive, absent, occasionally dishonest with his own team, and he also creates the conditions in which they do the best work of their lives.

Kidder does not resolve this. West is presented as effective and not admirable, which is a harder and more honest portrait than the genre usually attempts.

05

Mushroom management

The team's own name for West's approach: keep them in the dark and feed them manure. Information about corporate politics, competing projects and the machine's actual prospects was deliberately withheld.

The effect was to protect the team from distraction and to deny them information they had a legitimate interest in. Kidder reports both without adjudicating.

Keep them in the dark. It protected the team from distraction and denied them information they had a right to.

Devmark’s reading — not a quotation from the book
06

The cost

The book is honest about what the project took. Marriages strained, health neglected, several engineers leaving the company immediately after shipping, and a collective flatness at the end rather than triumph.

West's line about the process being a matter of no one being interested in the outcome once it arrived captures the deflation, which is the part of technical work least often written about.

07

What has dated

The technology completely — minicomputers, the specific architecture, the competitive landscape — and the workforce, which is almost entirely young, male and American in a way the book notices only faintly.

The deadline-driven heroics are also presented with less scepticism than a contemporary account would apply, and the book reads in places as celebrating a culture that has since been examined more critically.

08

What has not dated

The organisational dynamics, entirely. Ambiguous authority, informal status, the politics of interfaces between teams, the manager who manufactures urgency, and the specific psychology of committing to something difficult are all exactly recognisable.

Kidder's central insight — that people will work extraordinarily hard for an interesting problem and a sense of ownership, and that this can be elicited deliberately — remains the mechanism most technical organisations run on.

09

The writing

It is the reason the book won a Pulitzer. Kidder makes a computer's internals legible without simplifying them, and he is exceptional at conveying an engineer's relationship to a problem.

It is also a genuine work of literary journalism rather than a business book, which means it withholds lessons and lets the reader draw them.

10

What to take from it

The signing-up dynamic, recognised for what it is: a management technique that produces extraordinary effort by offering autonomy and an interesting problem, and that has a cost the person signing up rarely prices correctly.

And the flatness at the end, which is worth knowing about in advance by anyone who has attached a great deal to shipping something.

—

What to take away

  1. 01Autonomy plus a hard problem buys enormous effortKidder names it as a deliberate technique, and it remains what most technical organisations run on.
  2. 02The cost is rarely priced correctlyThe person signing up does the arithmetic badly, and usually knows they are doing it.
  3. 03Effective and admirable are differentWest creates the conditions for the team's best work and is not a good manager by any other measure.
  4. 04Interfaces are where organisations argueThe friction between the two sub-teams is the most recognisable organisational material in the book.
  5. 05Shipping is followed by flatnessThe deflation at the end is the part of technical work least often described and most often experienced.

Reading journey

A route through this idea

This book is not on a curated path, so the route below is derived from the catalogue: what comes before it, what goes further, and what approaches the same ground differently.

  1. You are hereThe Soul of a New Machine
  2. Go deeperCodeSame ground — Computing and History — and it assumes more of you.
  3. A different angleRefactoringAlso about Computing, but it reads as reference where that one is technical.
  4. Somewhere else entirelyAn Elegant PuzzleManagement and Computing travel together in this library, and this comes at it from the other side.

Nearby on the shelves

Related reading

↑↓ to move↵ to openesc to close