Cover of the summary of “The Soul of a New Machine”

Book summary “The Soul of a New Machine”: summary

Tracy Kidder

3,172 words · 18 min read

You want to understand how intense corporate environments drive technological innovation and personal sacrifice. In the late 1970s, the computer industry faced a massive shift as pioneering firms raced to build faster and cheaper machines.

Summary text

3,172 words · 18 min read

Introduction

You want to understand how intense corporate environments drive technological innovation and personal sacrifice. In the late 1970s, the computer industry faced a massive shift as pioneering firms raced to build faster and cheaper machines. Your primary challenge is navigating high-stakes engineering projects while managing corporate politics, tight deadlines, and exhausted teams.

A team of young engineers works punishing hours to design and build a revolutionary 32-bit minicomputer under immense corporate pressure.

Tracy Kidder's book details this grueling journey inside Data General during the development of a secret machine named Eagle. You will see how leaders inspire extreme dedication and how technical teams solve impossible hardware and software puzzles.

  • How do companies foster fierce loyalty among overworked employees?
  • What internal politics threaten breakthrough engineering projects?
  • How do young designers overcome hardware and software limitations?

1. Corporate Culture and Strategy

Data General projected extreme thriftiness while aggressively dominating the minicomputer market through volume discounts and rapid workforce expansion.

Data General designed its worldwide headquarters to project extreme corporate thriftiness and operational efficiency to investors.

You see this frugal aesthetic in the Westborough facility. It was constructed without an architect. Company engineers made it functional and cheap. It cost 19 dollars a square foot at a time when average commercial buildings in Massachusetts cost 34 dollars a foot.

Building 14A/B, also known as Webo, was built off Route 495 in Massachusetts. It featured security cameras and a sparse lobby displaying the first Nova computer.

The computer industry evolved from giant, centralized mainframes served by white-gloved intermediaries into decentralized minicomputers driven by affordable semiconductors. Early computers were large, expensive, and operated by small bands of professionals behind glass windows. The invention of the transistor and later integrated circuits allowed for smaller, highly reliable computers. This enabled scientists, engineers, and original equipment manufacturers to operate relatively inexpensive minicomputers themselves, bypassing traditional mainframe dominance by IBM.

IBM dominated early computing with large systems and its 360 line. New entrepreneurs built companies focused on minicomputers.

Data General was founded in 1968 by engineers who seceded from Digital Equipment Corporation after management rejected their new machine design. Edson de Castro led a team that designed DEC's successful PDP-8 minicomputer. When DEC's management turned down their new design, de Castro and other young engineers left to incorporate Data General. Within a year, they rented space in a former beauty parlor in Hudson, Massachusetts, and rapidly built a profitable enterprise.

Edson de Castro and Herb Richman teamed up with other engineers to start Data General, launching with an initial capital of $800,000.

Data General's founders strategically used stock and equity to retain financial security and fuel corporate growth rather than hoarding majority control.

The founders insisted that their lawyer invest his own money so he would remain committed to protecting them. Later, their lawyer insisted that each founder sell some of their holdings to take down a million dollars each. This financial cushion protected them from the paralyzing fear of losing everything and failing completely.

Herb Richman referred to the strategy of securing a million dollars in personal liquidity during stock offerings as the Fuck You Theory.

Data General distinguished itself from established competitors through aggressive marketing, unconventional advertisements, and steep volume discounts. Led by marketing director Allen Kluchman, Data General used brazen advertisements featuring company president Ed de Castro and deployed aggressive tactics at trade shows. They offered deep discounts to customers who bought machines in large quantities, bringing a fierce, competitive edge to the minicomputer market.

Data General published an ad featuring a stern photo of Ed de Castro stating they intended to make a lot of money, and later drafted an unpublished ad with the headline The Bastards Say, Welcome.

Rapid corporate growth in the computer industry creates severe operational risks, threatening to suffocate companies through production failures and strained resources. Computer companies had to grow rapidly just to stay alive, often increasing employee headcounts by massive margins annually. This hyper-growth strains management structures, production systems, and supply chains. Companies risk missing delivery commitments, ruining customer relationships, and disrupting business operations entirely.

Around 1973, Data General suffered severe shipment problems, missing commitments to customers and inadvertently putting some entrepreneurs out of business before recovering.

2. The Birth of Eagle

Tom West is an intense engineering leader who operates with exactness, high expectations, and a preference for crisis management. He communicates through precise gestures and vague statements, expecting engineers to operate on his secret wavelength.

Tom West rallied a demoralized team around a secret 32-bit project called Eagle to counter market panic and internal corporate politics.

DEC introduced the VAX 11/780, creating an existential market panic for Data General because you lacked a competing 32-bit supermini. Competitors threatened to lock in customers before you could enter the rapidly growing market.

West traveled to an undisclosed American city on a holiday morning in 1978, walked into a windowless room, and took apart a newly installed VAX CPU. He analyzed its printed-circuit boards and manufacturing costs, discovering a $22,500 estimated manufacturing cost for essential VAX hardware and a $100,000 retail price for a VAX.

The fundamental technical barrier for new minicomputers was expanding logical-address space from 16 bits to 32 bits. While 16-bit machines like Data General's NOVA and Eclipse could directly generate about 65,000 storage addresses, true 32-bit machines could address approximately 4.3 billion storage compartments.

Data General decided to relocate its major 32-bit project, the Fountainhead Project, to North Carolina, demoralizing the remaining New England engineers. CEO Edson de Castro praised North Carolina's lower operating costs and pro-business environment in the press, causing friction with the Massachusetts engineering staff who felt insulted by executive statements on a can-do attitude and a 20 percent cost-of-living difference.

Left behind in Massachusetts, a rebellious group of 5 engineers designed a secret, dual-personality machine called EGO to rival the 50-person North Carolina project. Using a mode bit, EGO functioned as both a standard 16-bit Eclipse and a high-speed 32-bit hot rod.

Engineers held the big shoot-out at HoJo's motor inn down south to fight for their processor design before executive management, but leadership ultimately rejected EGO in favor of the larger North Carolina team.

Maintaining software compatibility is critical because customers refuse to discard expensive, pre-existing software when upgrading hardware. IBM's 360 line introduced in the mid-1960s demonstrated that software-compatible computer families allow users to buy larger machines without rewriting system software or user programs. Data General made its Eclipse line upwardly compatible with NOVAs so old programs would run on newer machines.

West successfully pivoted his group by proposing Eagle, a fully Eclipse-compatible 32-bit machine built in secret under a 1 year timeline promised to executive management. Recognizing that incompatibility would force customers into market surveys with competitors, West rallied engineers around a machine that disguised its complexity under a compatible exterior while delivering high speed.

Carl Alsing helped launch Eagle by participating in West's meetings with vice presidents, steering them to approve the project as the viable alternative.

To secure corporate resources without triggering political opposition, West used dual messaging for the Eagle project:

  • Internal promotion inspired workers with glorious visions of a heroic breakthrough.
  • External promotion downplayed Eagle as a minor, low-risk insurance policy against potential failures in North Carolina.

Rosemarie Seale sorted through mail daily and protected the team from facility changes like moving mailrooms and remodeling to shield young engineers from bureaucratic distractions.

3. Building a Team

Data General housed its workers in Westborough headquarters featuring low, movable cubicle walls rather than closed offices. This layout allowed higher worker density per square foot and enabled management to reconfigure the space easily. Tom West noted that this layout created a cattle-yard environment and maintained a basic level of insecurity.

Management recruited inexperienced graduates and secured absolute dedication through a voluntary sign-up ritual.

Inspired by Seymour Cray's approach in Chippewa Falls, West and Alsing decided to recruit top graduates fresh out of school. This strategy had multiple benefits: novices commanded smaller salaries, possessed up-to-date knowledge, and their inexperience helped disguise the team's real intentions to rival competitors. West and Alsing recruited about a dozen neophytes from graduate schools of electrical engineering and computer science to work alongside veteran engineers. The total team included about thirty members, comprising about a dozen neophytes and a dozen or so old hands who had worked for West before.

Signing up meant agreeing to do whatever was necessary for the project's success, effectively volunteering labor rather than being coerced. Managers used this rite to ensure team members gave their heart and soul without management having to constantly push them. Carl Carman, the vice president of engineering, noted that the sign-up was necessary to ensure management was not conning anyone into overwork.

You can use a specific screening process to evaluate recruits:

  • Ask the recruit what they want to do and probe if they want to build a major computer.
  • Tell the recruit the bad news that the job will be tough and require long hours working with cynics.
  • Observe if the recruit shows fire in their eyes and insists they want to get in on the ground floor.
  • Let the candidate in after confirming they accept the high-pressure conditions.

Engineers on the Eagle project received no extra pay for working overtime and viewed stock options as mere sweeteners. They were motivated instead by the unique nature of the project, the casual dress code, flexible hours, and the opportunity to work on a major 32-bit machine. A newcomer started with a salary of $20,000 a year, while a veteran such as Alsing might make $30,000. Micro-kid Dave Keating chose Data General over IBM because IBM offered a minor memory chip improvement, whereas Data General offered a chance to work on a major backbone machine.

When Tom West was initially told he could not run the Eclipse Group because he had not designed a piece of equipment called an IOP, he retreated into his office, shut his door, and refused all social interactions for weeks until the design was complete. Carl Alsing repeatedly tried to invite West out for coffee during this period, but West rebuffed him with flat, calm replies before emerging seven weeks later with the completed IOP design.

4. Architecture and Design

An architecture defines what a machine will look like and do in detail for software writers rather than how it will physically be built. Drawing up this blueprint is the crucial first technical act in making a new computer. For the Eagle project, the machine needed to be a 32-bit, fully Eclipse-compatible computer with no mode bit.

Steve Wallach designed a clean 32-bit Eclipse architecture with structured memory protection while navigating corporate constraints.

Tom West identified Steve Wallach as the only person qualified to act as the architect for the 32-bit Eclipse computer, known as Eagle. Wallach worked on five different computer designs across various companies over a decade, but saw only one reach functional life, only for the customer to cancel further purchases. This history left him cynical about corporate project cancellations and initial constraints.

Wallach worked on the grand FHP machine for two years with a clean sheet of paper, only for the unfinished plans and designers to be moved to North Carolina, leading to the creation of EGO which was subsequently canceled by executive de Castro. Before agreeing to design a constrained system, an architect may demand direct confirmation from the company president to ensure the project will not be unexpectedly canceled later. Steve Wallach insisted on speaking directly with Data General president de Castro to confirm that a 32-bit Eclipse without a mode bit was genuinely desired and would be left alone.

A secure time-sharing computer system requires structured mechanisms to manage memory compartments and prevent users from accidentally corrupting data. Wallach adapted concepts from the MULTICS project and the VAX to create a simplified ring system. By merging segment numbers and ring numbers into the first three bits of a 32-bit address, he created eight security rings and eight segments that were cheap and efficient to implement.

Wallach used a yellow legal pad on his desk to draw diagrams of the standard 32-bit address, combining segment numbers with ring numbers to achieve his golden moment of design simplicity. Because management demanded full backward compatibility with older Eclipse instructions, Wallach and West developed routines where system programmers would formally request non-Eclipse-like instructions so the ideas appeared to originate from them. Wallach took ideas for new instructions to friends in System Software, who then wrote a memo to the Eclipse Group requesting the additions to protect the true authorship and intent.

Architects document their system specifications comprehensively, often personalizing the technical volumes with literary epigraphs that reflect their personal frustrations and philosophies. Wallach spent extensive time in the public library selecting classical and literary quotes from authors like Shakespeare and Tolkien to head each chapter of his two-hundred-page specification book. Wallach placed a quote from Macbeth regarding bloody instructions returning to plague the inventor at the top of the chapter about the instruction set.

5. The Mechanics of Programming

Programmers translated logical instructions into microcode using Boolean algebra while enduring intense compulsive habits.

Computers operate by comparing two values and performing actions based on conditional instructions. You rely on Boolean algebra to provide the logical framework for designing digital circuits made of transistor gates. Carl Alsing discovered Boolean algebra during his junior year at the University of Massachusetts.

Gates act like automatic barnyard gates that open or close based on control wire signals. These circuits perform binary arithmetic by using AND, NAND, OR, and NOR gates.

Microcode bridges the gap between high-level assembly instructions and the physical opening and closing of circuit gates. Modern computers translate assembly language into microcode consisting of long bit strings that control electrical signals inside microstorage. Trixie used microinstructions consisting of 75 bits stored in a microstorage compartment to execute commands. The Eclipse system contained 195 assembly-language instructions and 390 microinstructions.

Faced with writing massive volumes of microcode, Alsing would stall for months and experience mounting anxiety. Then he would seclude himself with manuals in a library to finish the entire project in a couple of weeks. Alsing encoded 195 assembly-language instructions into roughly 390 microinstructions during a two-week stint at the Boston Public Library.

Writing code can become an all-consuming addiction that leads young programmers to sacrifice sleep and relationships. Carl Alsing and about ten other male undergraduates became midnight programmers at their university's IBM computer room, ultimately causing Alsing to flunk out.

Complex computer programs like Adventure simulate labyrinthine worlds that hook users into map-making and deep problem-solving. The game Adventure creates an underground world called Colossal Cave where players navigate using two-word commands, map out twisty passages, and encounter obstacles like trolls and mazes. You might play Adventure in the basement of Westborough late at night under the supervision of Carl Alsing.

Corporate environments often practice the mushroom theory of management, keeping workers in the dark and feeding them poorly. To counter this grueling atmosphere, Alsing acted as a social director for the Microteam. Team members built camaraderie and released technical tension by engaging in terminal-based pranks and hacking contests known as Tube Wars. Bob Beauchamp bypassed Alsing's double-encrypted files by modifying Trixie's operating system to automatically send unencrypted copies of Alsing's messages to Beauchamp's files.

6. Debugging and Delivery

As the project enters its final months, momentum slows and problems take days to uncover. You experience deep cumulative fatigue that standard rest cannot clear.

The team overcame complex debugging hurdles, supply chain risks, and severe burnout to deliver the finished machine.

Jon Blau and Ed Rasala discuss their persistent tiredness during this grind. Four prototypes are available for debugging, and thirty or so software engineers wait for the hardware to be shipped to the Software Department.

A critical diagnostic failure occurs when an interrupt routine attempts to cross memory blocks. Jim Guyer notices that Coke has one more memory module than Gollum, leading to the realization that the prototype fell off the end of the world.

An elusive flakey bug that causes intermittent crashes is finally resolved on October 6. Executive Carl Carman grasps the ALU board by its edges and shakes it, leading Guyer, Holberger, and Rasala to replace all the sockets holding the chips in the center of the ALU.

When standard trace methods fail because the root cause happened far back in time, you must switch tactics. You can follow these steps to isolate the fault:

  • Hook up logic analyzers to various parts of the machine and set them to trigger snapshots upon failure.
  • Run the program up to the target pass or iteration.
  • Have the machine stop every time a specific subroutine call and return occurs to obtain console printouts and analyzer pictures.
  • Compare tag numbers between the Instruction Processor and System Cache to verify consistency.

Jim Veres produces a massive heap of continuous computer paper streaming from Gollum's console by having the machine stop at every JSR and Return during the 122nd iteration. On October 8, Gallifrey Eagle is loaded onto a dolly and wheeled to the Software Department. By early 1981, Eagle orders represent 10 percent of the value of all new orders for Data General equipment.

A complex computer project culminates in a massive volume of distinct microcode, software libraries, schematics, and testing materials.

The final output includes 4,096 lines of microcode, over 200,000 lines of system software, about 240 pages of schematics, and twenty hours of videotape. Data General publicly announces Eagle at the Roosevelt Hotel in New York City, renaming the machine the Eclipse MV/8000. At the New York debut featuring 128 terminals hooked to a single machine, the system briefly crashes but is fixed so deftly by engineers that the audience never notices.

As the Eclipse Group disbands, key members experience postpartum blues and career shifts. When West moves to an upstairs office, Alsing, Rasala, and Blau escort his oak-cased clock in a cart up to his new windowless room, feeling as though they are attending a funeral.

10 Key Ideas

  1. Data General designed its worldwide headquarters to project extreme corporate thriftiness and operational efficiency to investors.
  2. Data General's founders strategically used stock and equity to retain financial security and fuel corporate growth rather than hoarding majority control.
  3. Tom West rallied a demoralized team around a secret 32-bit project called Eagle to counter market panic and internal corporate politics.
  4. Management recruited inexperienced graduates and secured absolute dedication through a voluntary sign-up ritual.
  5. Steve Wallach designed a clean 32-bit Eclipse architecture with structured memory protection while navigating corporate constraints.
  6. Programmers translated logical instructions into microcode using Boolean algebra while enduring intense compulsive habits.
  7. The team overcame complex debugging hurdles, supply chain risks, and severe burnout to deliver the finished machine.
  8. A complex computer project culminates in a massive volume of distinct microcode, software libraries, schematics, and testing materials.
  9. Data General publicly announced Eagle at the Roosevelt Hotel in New York City, renaming the machine the Eclipse MV/8000.
  10. As the Eclipse Group disbanded, key members experienced postpartum blues and career shifts.

A summary is an independent retelling, not the text of the book.

Cover of the summary of “The Last Whalers” 20 min read

The Last Whalers

Doug Bock Clark
Cover of the summary of “Confess” 21 min read

Confess

Rob Halford
Cover of the summary of “Toast” 17 min read

Toast

Nigel Slater
Cover of the summary of “Ace Voices” 24 min read

Ace Voices

Eris Young
Cover of the summary of “For Small Creatures Such as We” 17 min read
Cover of the summary of “Two Trees Make a Forest” 16 min read
Cover of the selected audiobook Choose a chapter The player is ready
0:00 0:00

Volume