What do you think?
Rate this book
The Soul of a New Machine
The computer revolution brought with it new methods of getting work done—just look at today's news for reports of hard-driven, highly-motivated young software and online commerce developers who sacrifice evenings and weekends to meet impossible deadlines. Tracy Kidder got a preview of this world in the late 1970s when he observed the engineers of Data General design and build a new 32-bit minicomputer in just one year. His thoughtful, prescient book, The Soul of a New Machine, tells stories of 35-year-old "veteran" engineers hiring recent college graduates and encouraging them to work harder and faster on complex and difficult projects, exploiting the youngsters' ignorance of normal scheduling processes while engendering a new kind of work ethic.
These days, we are used to the "total commitment" philosophy of managing technical creation, but Kidder was surprised and even a little alarmed at the obsessions and compulsions he found. From in-house political struggles to workers being permitted to tease management to marathon 24-hour work sessions, The Soul of a New Machine explores concepts that already seem familiar, even old-hat, less than 20 years later. Kidder plainly admires his subjects; while he admits to hopeless confusion about their work, he finds their dedication heroic. The reader wonders, though, what will become of it all, now and in the future. —Rob Lightner
These days, we are used to the "total commitment" philosophy of managing technical creation, but Kidder was surprised and even a little alarmed at the obsessions and compulsions he found. From in-house political struggles to workers being permitted to tease management to marathon 24-hour work sessions, The Soul of a New Machine explores concepts that already seem familiar, even old-hat, less than 20 years later. Kidder plainly admires his subjects; while he admits to hopeless confusion about their work, he finds their dedication heroic. The reader wonders, though, what will become of it all, now and in the future. —Rob Lightner
293 pages, Paperback
First published January 1, 1981
About the author
Tracy Kidder
42 books1,216 followersTracy Kidder is an American author and Vietnam War veteran. Kidder may be best known, especially within the computing community, for his Pulitzer Prize-winning The Soul of a New Machine, an account of the development of Data General's Eclipse/MV minicomputer. The book typifies his distinctive style of research. He began following the project at its inception and, in addition to interviews, spent considerable time observing the engineers at work and outside of it. Using this perspective he was able to produce a more textured portrait of the development process than a purely retrospective study might.
Kidder followed up with House, in which he chronicles the design and construction of the award-winning Souweine House in Amherst, Massachusetts. House reads like a novel, but it is based on many hours of research with the architect, builders, clients, in-laws, and other interested parties.
In 2003, Kidder also published Mountains Beyond Mountains: The Quest of Dr. Paul Farmer, A Man Who Would Cure The World after a chance encounter with Paul Farmer. The book was held to wide critical acclaim and became a New York Times bestseller. The actor Edward Norton has claimed it was one of the books which has had a profound influence on him.
Kidder followed up with House, in which he chronicles the design and construction of the award-winning Souweine House in Amherst, Massachusetts. House reads like a novel, but it is based on many hours of research with the architect, builders, clients, in-laws, and other interested parties.
In 2003, Kidder also published Mountains Beyond Mountains: The Quest of Dr. Paul Farmer, A Man Who Would Cure The World after a chance encounter with Paul Farmer. The book was held to wide critical acclaim and became a New York Times bestseller. The actor Edward Norton has claimed it was one of the books which has had a profound influence on him.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 707 reviews
November 13, 2015
I can't believe this is not required reading for a computer architecture course!
In my high school Biology, H.G. Wells' The Time Machine was assigned to be read over the winter vacation. It was a bit of a stretch, but did make the class a bit more interesting. As I read Kidder describe the toil undertaken in creating this new computer - working under the pressure on the brink of insanity to find those incessant bugs - I thought this the perfect companion for the CS154B Computer Architecture class at UC Davis. As students, we worked on analogous type of problems and under similar conditions: this book provides a human angle to that struggle. If I recall correctly, pipelining is explained so well, I bet my grandma would even understand it! And yet there are plenty of subtle technical details buried in this masterfully written true story.
In my high school Biology, H.G. Wells' The Time Machine was assigned to be read over the winter vacation. It was a bit of a stretch, but did make the class a bit more interesting. As I read Kidder describe the toil undertaken in creating this new computer - working under the pressure on the brink of insanity to find those incessant bugs - I thought this the perfect companion for the CS154B Computer Architecture class at UC Davis. As students, we worked on analogous type of problems and under similar conditions: this book provides a human angle to that struggle. If I recall correctly, pipelining is explained so well, I bet my grandma would even understand it! And yet there are plenty of subtle technical details buried in this masterfully written true story.
December 24, 2013
As a shameless Tracy Kidder fan, I found this book quite extraordinary. Written in 1981, it chronicles the building of a 32-bit microcomputer at Data General. This was a time when the competitive environment for computer advancement was heating up to a furious pace. Today, these times read like ancient history, exceptt for the fact that it was the dawning of an age.
Tracy Kidder, a journalist, not a computer engineer, took on the task of capturing the new computer building process when it was part science, part art, and to some extent part magic. His Pulitzer Prize winning book puts lightning in a bottle. What we see is what builder-engineering is about, how the lure of building a new machine becomes a drug, how the challenge of problems (design, debugging)take over the engineer's life, and how managers must manage with both a strong hand and a loose grip simultaneously.
The mental and emotional stress that becomes the engineer's life, the almost fraternity-like antics that take place to lessen that stress, and the demands of producing a functioning and profitable machine dominate the realities described in the book. We read about the vision for the new machine, the challenges of getting upper management to fund what they don't think can be done, the excruciating deadlines that must be met, the overwhelming frustrations during break-fix times, and the idiosyncrasies of the players.
I was left in awe of the process, both technical and managerial, and inspired by the creative spirit of professionals who are willing to invest their souls into their creations, no matter what.
Tracy Kidder, a journalist, not a computer engineer, took on the task of capturing the new computer building process when it was part science, part art, and to some extent part magic. His Pulitzer Prize winning book puts lightning in a bottle. What we see is what builder-engineering is about, how the lure of building a new machine becomes a drug, how the challenge of problems (design, debugging)take over the engineer's life, and how managers must manage with both a strong hand and a loose grip simultaneously.
The mental and emotional stress that becomes the engineer's life, the almost fraternity-like antics that take place to lessen that stress, and the demands of producing a functioning and profitable machine dominate the realities described in the book. We read about the vision for the new machine, the challenges of getting upper management to fund what they don't think can be done, the excruciating deadlines that must be met, the overwhelming frustrations during break-fix times, and the idiosyncrasies of the players.
I was left in awe of the process, both technical and managerial, and inspired by the creative spirit of professionals who are willing to invest their souls into their creations, no matter what.
January 19, 2020
West would sit at his desk and stare for hours at the team’s drawings of the hardware, playing his own mind games with the results of the other engineers’ mind games. Will this work? How much will this cost? Once, someone brought a crying baby past his door, and afterward it took him an hour to retrace his steps through the circuit design he had been pondering. Laughter outside often had the same effect, once in a while it made his hands shake with rage — especially if he didn’t like the design he’d been staring at.
West usually drove out of Westborough fast after work. “I can’t talk about the machine,” he said one evening, bent forward over the steering wheel. “I’ve gotta keep life and computers separate, or else I’m gonna go mad.”
In 1981 Tracy Kidder penned this non-fiction narrative and won the Pulitzer Prize. The story is about a group of engineers, who work for Data General outside Boston, as they spend a year designing a better mini-computer.
You probably haven’t heard of Data General because they never got as big as IBM, Cray, NEC and Data General missed the personal computing revolution that unfolded in the immediate years after this book was published.
This is not a dramatic book about overpaid and soul-less individuals at high powered tech companies. Nor is it a book about visionaries like Bill Gates or Steve Jobs.
No this book is quite literally about a group of a dozen engineers led by their veteran manager Tom West. This group works at the Boston branch of Data General. They are given a year to build a better and faster version of their minicomputer so they can get a leg up on their rival DEC and DEC’s newly released VAX minicomputer. The team is to employ some secrecy initially and not to let a parallel team at the headquarters in North Carolina know what they are working on. In part because they were already told their project is redundant.
Although the topic may seem mundane to some, Kidder’s storytelling and narrative is genuine, well paced and compelling in the human sense. The author was embedded in the group so we get a linear narrative and first hand observations on the quest to build a new computer in twelve months. We also get to know the people and their personalities.
As far as nerd-fare there is a bit related to circuit design but not enough to spoil the story. Maybe a few mentions of NAND gates and a good deal of discussion on related computer components. I would say one does not have to be tech savvy to love the book but a curiosity about how organizations work and what motivates scientists and engineers is necessary.
5 stars. Excellent read. Although the industry around mini-computers died decades ago, this narrative is arguably the best literary style writing on tech that I have read in years. I am adding several other Tracy Kidder books to my to-read shelf. The story is four decades old, but this should be required reading for anyone in the tech industry.
West usually drove out of Westborough fast after work. “I can’t talk about the machine,” he said one evening, bent forward over the steering wheel. “I’ve gotta keep life and computers separate, or else I’m gonna go mad.”
In 1981 Tracy Kidder penned this non-fiction narrative and won the Pulitzer Prize. The story is about a group of engineers, who work for Data General outside Boston, as they spend a year designing a better mini-computer.
You probably haven’t heard of Data General because they never got as big as IBM, Cray, NEC and Data General missed the personal computing revolution that unfolded in the immediate years after this book was published.
This is not a dramatic book about overpaid and soul-less individuals at high powered tech companies. Nor is it a book about visionaries like Bill Gates or Steve Jobs.
No this book is quite literally about a group of a dozen engineers led by their veteran manager Tom West. This group works at the Boston branch of Data General. They are given a year to build a better and faster version of their minicomputer so they can get a leg up on their rival DEC and DEC’s newly released VAX minicomputer. The team is to employ some secrecy initially and not to let a parallel team at the headquarters in North Carolina know what they are working on. In part because they were already told their project is redundant.
Although the topic may seem mundane to some, Kidder’s storytelling and narrative is genuine, well paced and compelling in the human sense. The author was embedded in the group so we get a linear narrative and first hand observations on the quest to build a new computer in twelve months. We also get to know the people and their personalities.
As far as nerd-fare there is a bit related to circuit design but not enough to spoil the story. Maybe a few mentions of NAND gates and a good deal of discussion on related computer components. I would say one does not have to be tech savvy to love the book but a curiosity about how organizations work and what motivates scientists and engineers is necessary.
5 stars. Excellent read. Although the industry around mini-computers died decades ago, this narrative is arguably the best literary style writing on tech that I have read in years. I am adding several other Tracy Kidder books to my to-read shelf. The story is four decades old, but this should be required reading for anyone in the tech industry.
June 27, 2015
Books written by journalists in general and non-fiction Pulitzer winners in particular are—in my experience—universally garbage, but this was a specific recommendation, so I thought I'd give it a try. I shouldn't have.
The Soul of a New Machine describes the development process of Data General's Eclipse MV/8000, but Kidder has no particular insight into the industry or any specific aspect of hardware development. Like most journalists, he does have a tremendous capacity for taking deeply shitty people at their word when it comes to their deeply shitty practices, though.†
He was obviously handed a large amount of technical information, and while he should be commended for not just cutting it out (even if his attempts to make it accessible are of dubious value), none of it adds anything to the narrative.
The reason this book was recommended to me was because the person who recommended it believes it gives a great impression of what this kind of deadline-bound creative development is (and, implicitly, should be) like, not just in hardware design, but in every sector that makes new things.
If that is true for you (it hasn't been for me), I can only feel sorry for you. Don't put up with that kind of bullshit, and definitely don't celebrate it. What the book describes is semi-voluntary slavery, and even Kidder recognises it as a recipe for an early burn-out.
--------
† Data General, as you may not remember, was notorious for its generally unpleasant business practices (towards its competitors, clients, and employees alike), and ultimately accomplished nothing of any lasting consequence before finally disappearing into EMC.
The Soul of a New Machine describes the development process of Data General's Eclipse MV/8000, but Kidder has no particular insight into the industry or any specific aspect of hardware development. Like most journalists, he does have a tremendous capacity for taking deeply shitty people at their word when it comes to their deeply shitty practices, though.†
He was obviously handed a large amount of technical information, and while he should be commended for not just cutting it out (even if his attempts to make it accessible are of dubious value), none of it adds anything to the narrative.
The reason this book was recommended to me was because the person who recommended it believes it gives a great impression of what this kind of deadline-bound creative development is (and, implicitly, should be) like, not just in hardware design, but in every sector that makes new things.
If that is true for you (it hasn't been for me), I can only feel sorry for you. Don't put up with that kind of bullshit, and definitely don't celebrate it. What the book describes is semi-voluntary slavery, and even Kidder recognises it as a recipe for an early burn-out.
--------
† Data General, as you may not remember, was notorious for its generally unpleasant business practices (towards its competitors, clients, and employees alike), and ultimately accomplished nothing of any lasting consequence before finally disappearing into EMC.
March 12, 2010
The Soul of A New Machine is an engineers soap opera following a rag-tag team of neophytes driven by their own Captain Ahab to build a revolutionary 32-bit computer for the now-defunct Data General in the late 1970s. Tracey Kiddler, the author, was given a rare opportunity as a journalist to follow the team's progress from within and his story shows an insiders knowledge. He breaks down the complex technical nature of the task through a series of straightforward analogies and by doing so enables us to follow the human struggle of these mistreated engineers, who, driven by manipulation and pride work mad hours with little benefit to themselves to breathe life into a machine of their very own. But we are not made to feel bad for the men who sacrifice 2 years of their lives to this white-whale. Instead we come to realize the insane genius and compassion of their caption, Tom West, who has sheltered them from the menacing bureaucracy that surrounds them and given them a sense of purpose and ownership, an opportunity not often bestowed on fresh out of school college grads. Together they band together, go to war, and ultimately emerge bloody, beat-up, and victorious.
Important Lessons:
1. Important projects are easy to recruit for.
2. Work runs on peer pressure.
3. Everyone wants to feel an ownership of their project.
Important Lessons:
1. Important projects are easy to recruit for.
2. Work runs on peer pressure.
3. Everyone wants to feel an ownership of their project.
May 3, 2018
This is the 2nd time I've read this book and it took on a new meaning after being part of a huge AWS product launch. The feeling of camaraderie, pride, and purpose was something that I had just recently experienced which made me relate to the engineers and managers in a different way.
I loved it the first time I read it but somehow was able to love it more. At the time I didn't understand the historical context accurately. I've recently been reading about the timeline of computers which was a big help. Knowing this was in the late 70s is important because this was the rise of the personal computer and the slow death of the minicomputer.
I think it is easy to overlook this book and not understand it for what it was at the time. Computers were still foreign and not many people owned them. They were in lots of workplaces but not everyone had access to them.
This book won a Pulitzer which was surprising to me before I had read it. It was hard to believe a book about a bunch of nerds building a computer would win the prestigious award but you quickly understand how it did this after the preface of the book. Kidder starts the story by introducing the main character, Tom West, an enigmatic man on a boat off the East Coast with a group of strangers as they sail the sea. It expertly foreshadows West's character and his role as the general manager of the computer the book documents. Without ever mentioning a computer you start to wonder if you picked up the wrong book.
I wish another company would open its doors to a skilled storyteller like Kidder. Chronicling a software startup or the creation of a large service at a big company in the same way would be a riveting read given the advancement of tech.
I really recommend this book and consider it one of my favorites. Kidder is an expert at his craft and seamlessly blends the team's stories into the story of the company, Data General, and that into the overarching story of the industry.
I loved it the first time I read it but somehow was able to love it more. At the time I didn't understand the historical context accurately. I've recently been reading about the timeline of computers which was a big help. Knowing this was in the late 70s is important because this was the rise of the personal computer and the slow death of the minicomputer.
I think it is easy to overlook this book and not understand it for what it was at the time. Computers were still foreign and not many people owned them. They were in lots of workplaces but not everyone had access to them.
This book won a Pulitzer which was surprising to me before I had read it. It was hard to believe a book about a bunch of nerds building a computer would win the prestigious award but you quickly understand how it did this after the preface of the book. Kidder starts the story by introducing the main character, Tom West, an enigmatic man on a boat off the East Coast with a group of strangers as they sail the sea. It expertly foreshadows West's character and his role as the general manager of the computer the book documents. Without ever mentioning a computer you start to wonder if you picked up the wrong book.
I wish another company would open its doors to a skilled storyteller like Kidder. Chronicling a software startup or the creation of a large service at a big company in the same way would be a riveting read given the advancement of tech.
I really recommend this book and consider it one of my favorites. Kidder is an expert at his craft and seamlessly blends the team's stories into the story of the company, Data General, and that into the overarching story of the industry.
May 31, 2015
In the early 1980's when this book was first published, the author had to communicate the complexity and labors experienced by a group of engineers as they developed the next big thing for a second rate company. Most of those who read this book today have a level of computer literacy that may be beyond what the author's computer literacy was when he wrote the book. Consequently there are sections where the author takes great care to convey computer concepts and operations to a reader who has never seen a computer. The modern reader might find such sections quaint or boring, while a few others, who had lived through those times will find the detail and care a nostalgic visit to past lives. Bear with the author as he describes the ins and outs of Adventure and intricacies of machines that have become dinosaurs in the pantheon of technology.
As so many other reviewers have mentioned, the highlight of the book is the team and interpersonal dynamics--human drama that can be found in pressure cooker development environments today. This portion of the book is as relevant and insightful as it was in 1981.
The one message that has stuck with me several weeks after having read the book is "Pinball is what counted". The rule of pinball is that if you win, you get to play again. "You win one game, you get to play another." Playing the game is a powerful motivator for a select few individuals. Many readers may find it difficult to understand why the team took on such a challenge, but there are a few who will recognize the thrill of pinball and understand the siren song of working in difficult environments on challenges that might be near impossible to achieve.
As so many other reviewers have mentioned, the highlight of the book is the team and interpersonal dynamics--human drama that can be found in pressure cooker development environments today. This portion of the book is as relevant and insightful as it was in 1981.
The one message that has stuck with me several weeks after having read the book is "Pinball is what counted". The rule of pinball is that if you win, you get to play again. "You win one game, you get to play another." Playing the game is a powerful motivator for a select few individuals. Many readers may find it difficult to understand why the team took on such a challenge, but there are a few who will recognize the thrill of pinball and understand the siren song of working in difficult environments on challenges that might be near impossible to achieve.
January 15, 2019
“A feeling of accomplishment” is what Veres says he has. “But then again, there’s lots more feeling of accomplishment to go.”
The underlying theme of this book, if there is one, would seem to me to be the general feeling that your work needs to have meaning to you. This is a view, in a variety of ways, that most of the engineers seem to hold at this company. The company being Data General, a company I had never heard of, but apparently was quite a big deal in the late 70's and early 80's.
In my own experiences I consistently hear engineers tell me they want a job which allows them to do what they want, which isn't working. My view and a view that seems to be held at everyone at Data General in the early 80's is that's bullshit. I decided to studying computer science and computer engineering because five years ago I was afraid I wouldn't accomplish anything of meaning to the world before I die. As I sit with less than a year before I complete these majors I expect to find meaning and satisfaction from my work, to do that I'm going to have to continue working as hard as I can for as long as I can.
The paradox of choice can get in the way of this search for meaning. We're presented with so many choices that we forget that confusion is natural and fear is normal. These men and women in this novel were on a journey to find themselves and they accomplished that by changing their industry. They weren't for money, although much of it would be found by some, they were looking for meaning. That's what matters.
You shouldn't spend your life waiting to pass the time, or even worse waiting for some final judgement at the end, the real judgement comes everyday.
The underlying theme of this book, if there is one, would seem to me to be the general feeling that your work needs to have meaning to you. This is a view, in a variety of ways, that most of the engineers seem to hold at this company. The company being Data General, a company I had never heard of, but apparently was quite a big deal in the late 70's and early 80's.
In my own experiences I consistently hear engineers tell me they want a job which allows them to do what they want, which isn't working. My view and a view that seems to be held at everyone at Data General in the early 80's is that's bullshit. I decided to studying computer science and computer engineering because five years ago I was afraid I wouldn't accomplish anything of meaning to the world before I die. As I sit with less than a year before I complete these majors I expect to find meaning and satisfaction from my work, to do that I'm going to have to continue working as hard as I can for as long as I can.
The paradox of choice can get in the way of this search for meaning. We're presented with so many choices that we forget that confusion is natural and fear is normal. These men and women in this novel were on a journey to find themselves and they accomplished that by changing their industry. They weren't for money, although much of it would be found by some, they were looking for meaning. That's what matters.
You shouldn't spend your life waiting to pass the time, or even worse waiting for some final judgement at the end, the real judgement comes everyday.
January 11, 2014
It is a testament to Tracy Kidder's skills as a writer that I found a book of ancient computer engineering to be a compelling read. The story of Data General's development of a 32-bit minicomputer was somehow rendered like an adventure story through a wild landscape filled with thrills and dangers and eventual reward.
I read this book as background reading for a trilogy of books I'm reviewing and so pleasant to find such enjoyment in my research.
Oh, and the book also won the Pulitzer Prize...
I read this book as background reading for a trilogy of books I'm reviewing and so pleasant to find such enjoyment in my research.
Oh, and the book also won the Pulitzer Prize...
Read
September 19, 2022Read this years ago. I remember enjoying it.
February 22, 2018
It's the late 1970s, and minicomputer maker Data General is in trouble. Their machines are getting long in the tooth; programs are bumping up against the memory limit of the 16-bit architecture. Who could've thought that 64 kilobytes of RAM wouldn't be enough? In desperation, a team in North Carolina was tasked with building a modern, 32-bit machine capable of addressing up to 4GB. In revenge, the passed-over team in Massachusetts decided they would build another 32-bit machine, on simpler lines, and show up the Carolinians.
Both in desperation and Massachusetts was Tracy Kidder, a hopeful author whose first book had stunk. "How about computers?" suggested his editor. So Kidder called up his old roommate, who by luck was starting up Team Revenge, and embedded himself in that project.
I had the good fortune to be in the computer field during the crazed internet boom, and have done my time in startups. It was exciting, interesting, strange, and awfully similar to what Kidder described decades ago. "The Soul of the New Machine" is that of the engineers, who poured themselves into it day after day, late hour by late hour.
Kidder won a well-deserved Pulitzer prize for this. If you're interested in the sort of people and environment surrounding the bleeding edge of the computer industry, you should give it a shot.
Wired has an appreciation/where-they-are-now (or were) for the main players here: https://www.wired.com/2000/12/soul/
and a one for the others here: https://www.wired.com/2000/12/eagleteam/
Both in desperation and Massachusetts was Tracy Kidder, a hopeful author whose first book had stunk. "How about computers?" suggested his editor. So Kidder called up his old roommate, who by luck was starting up Team Revenge, and embedded himself in that project.
I had the good fortune to be in the computer field during the crazed internet boom, and have done my time in startups. It was exciting, interesting, strange, and awfully similar to what Kidder described decades ago. "The Soul of the New Machine" is that of the engineers, who poured themselves into it day after day, late hour by late hour.
Kidder won a well-deserved Pulitzer prize for this. If you're interested in the sort of people and environment surrounding the bleeding edge of the computer industry, you should give it a shot.
Wired has an appreciation/where-they-are-now (or were) for the main players here: https://www.wired.com/2000/12/soul/
and a one for the others here: https://www.wired.com/2000/12/eagleteam/
March 28, 2019
Portrayal of a high-pressure hardware development project. It's...fine. Most interesting bit is definitely at the end where Kidder muses about the telos of work, and why people might voluntarily give so much of themselves for a project. Ruskin thought that Gothic cathedrals had been built by people who saw meaning in their labour, something industrialisation had taken away from them. The development of this computer was mainly driven by employee enthusiasm, and remote managers relying on the "mushroom principle" (leave them in the dark, feed them manure, and watch them grow).
Shows the tech industry pretty much as it is today: mostly white/male, a world of affable smart nerds who enjoy what they do and work long hours out of personal interest in their work, not employer pressure. It's basically an anthropological study, written without much technical background (Kidder tries to convey any technical ideas by very simple analogies). He cites John McPhee as his* primary writing influence, and that kind of slow pensive writing might be better suited to writing about the outdoors than corporate IT.
*I thought I could add another to my quorum of books by female authors this year, but it turns out that Tracy is just one of those starchy WASP men's names, like Hilary or Lynn.
Shows the tech industry pretty much as it is today: mostly white/male, a world of affable smart nerds who enjoy what they do and work long hours out of personal interest in their work, not employer pressure. It's basically an anthropological study, written without much technical background (Kidder tries to convey any technical ideas by very simple analogies). He cites John McPhee as his* primary writing influence, and that kind of slow pensive writing might be better suited to writing about the outdoors than corporate IT.
*I thought I could add another to my quorum of books by female authors this year, but it turns out that Tracy is just one of those starchy WASP men's names, like Hilary or Lynn.
July 11, 2011
(4.0) Snapshot in time in the history of computing
Retells the story of the development of the first 32-bit minicomputer offering from Data General (I'm not nerdy/old enough to really know about them). Much of it centers on the defiant attitude that the engineers took to build this computer even when it appeared that Data General was doing its best not to make it happen (relatively low pay, few resources, few engineers, crazy deadline). But they do (only about 50% over schedule), through allnighters, double-shifts, worked weekends and a heck of a good bunch of engineers.
Kidder delves into some of the technical problems and solutions they encountered, which were interesting. But the most interesting thing for me was that this was right around the time that marked the end of the ability for a single engineer to really know the entire CPU...they're getting into the territory where there just need to be some black boxes that you know about but know little of in order to get everything to work together.
One other interesting section is towards the end when Kidder tries to debunk the notion of a "computer revolution". Just ten years later, he could probably see that he was just witnessing the very beginning of a series of revolutions.
Well written, interesting, I'll probably try another Tracy Kidder sometime soon. Anyone have a strong recommendation?
Retells the story of the development of the first 32-bit minicomputer offering from Data General (I'm not nerdy/old enough to really know about them). Much of it centers on the defiant attitude that the engineers took to build this computer even when it appeared that Data General was doing its best not to make it happen (relatively low pay, few resources, few engineers, crazy deadline). But they do (only about 50% over schedule), through allnighters, double-shifts, worked weekends and a heck of a good bunch of engineers.
Kidder delves into some of the technical problems and solutions they encountered, which were interesting. But the most interesting thing for me was that this was right around the time that marked the end of the ability for a single engineer to really know the entire CPU...they're getting into the territory where there just need to be some black boxes that you know about but know little of in order to get everything to work together.
One other interesting section is towards the end when Kidder tries to debunk the notion of a "computer revolution". Just ten years later, he could probably see that he was just witnessing the very beginning of a series of revolutions.
Well written, interesting, I'll probably try another Tracy Kidder sometime soon. Anyone have a strong recommendation?
March 6, 2018
Hard to believe that it's coming up for 35 years since the events in this book took place. It was a different time. A time when the frontiers in computer hardware were open and worth fighting for; when margins in hardware were, by present day standards, stratospheric, and when computer professionals/nerds/geeks were cheap and in it for the challenge. This is the true story of a small team of people with a common goal - to give birth to a new computer that will save a company. The different characters in the book have different perspectives, different drivers, but they all gave a part of themselves to see their baby born. The baby was the 32-bit Eclipse, (the now defunct) Data General's chance to survive a few more years in the nascent mini/micro computer industry. While the book has sufficient technical information to keep the casual geek interested, the real story is about the engineers working 100 hour weeks and how this project became a big part of their lives. Kidder has created a classic of the mini-computer era that has no equal.
April 15, 2011
Fantastic!
March 27, 2024
This book made me very very happy.
Tracy Kidder gets you supremely invested in not just the engineering challenge of making the Eagle at Data General in the late 70s, but also in every single person involved in the process. The book’s focus on individual experiences that made this stubborn band of engineers tick and devote all of themselves to building a computer, from design to debugging in a very short span of time left me teary-eyed.
It shows through every page how much time Tracy Kidder spent with the team that was actually building the machine. He chronicled their progress, not shying away from the minutiae of computer architecture concepts. For someone who was once deep in love with Computer Architecture, reading the book was an emotional experience.
I’m glad I did not read this book earlier and I’ll be sure to come back to it again in the future.
Tracy Kidder gets you supremely invested in not just the engineering challenge of making the Eagle at Data General in the late 70s, but also in every single person involved in the process. The book’s focus on individual experiences that made this stubborn band of engineers tick and devote all of themselves to building a computer, from design to debugging in a very short span of time left me teary-eyed.
It shows through every page how much time Tracy Kidder spent with the team that was actually building the machine. He chronicled their progress, not shying away from the minutiae of computer architecture concepts. For someone who was once deep in love with Computer Architecture, reading the book was an emotional experience.
I’m glad I did not read this book earlier and I’ll be sure to come back to it again in the future.
June 12, 2019
It's surprising how a book from 1981 about a team of engineers developing a new computer (a competitor to the DEC VAX) is still very relevant and entertaining. Obviously the technical details reflect the technology of the 1970s (the features of the new machines - a 32-bit architecture with protection rings and support to threads are very common today), but what gave a Pulitzer Prize to this book is the description of the people involved in the development process, what motivated them and how is the life in the engineering department of a hardware company.
If Hackers: Heroes of the Computer Revolution tells the early computers history from the academic, hobbyist and domestic point-of-view, The Soul of a New Machine chronicles the other side, the commercial/industry perspective. And it's easy to perceive, common and central to both books, the "Hacker Ethics", the desire of solving new and interesting problems and develop new machines - something that persists to this day.
If Hackers: Heroes of the Computer Revolution tells the early computers history from the academic, hobbyist and domestic point-of-view, The Soul of a New Machine chronicles the other side, the commercial/industry perspective. And it's easy to perceive, common and central to both books, the "Hacker Ethics", the desire of solving new and interesting problems and develop new machines - something that persists to this day.
January 23, 2020
Single-digits-year-old me really liked the title. So I read it.
It's a little hard not to view this work environment as toxic, despite the obvious love the author has for the project. Sadly, a lot of the love for a project like this one became the go-to idea that eventually fueled much that is worst in the tech industry. 70 hour work weeks as the expected norm? Check. In this book we have recent-grads who are exploited for their willingness to try anything-- which has now become using interns as slave labor. The vision of everyone one-day owning a personal computer that they can carry around with them? Check. The myopia of loving work on a great project with no broader understanding or concern for how that technology is going to be used? Check.
In this era of big beige clunkers, glowing green type, and rainbow cord-spaghetti were the seeds of the world we know and love. And love to hate.
It's a little hard not to view this work environment as toxic, despite the obvious love the author has for the project. Sadly, a lot of the love for a project like this one became the go-to idea that eventually fueled much that is worst in the tech industry. 70 hour work weeks as the expected norm? Check. In this book we have recent-grads who are exploited for their willingness to try anything-- which has now become using interns as slave labor. The vision of everyone one-day owning a personal computer that they can carry around with them? Check. The myopia of loving work on a great project with no broader understanding or concern for how that technology is going to be used? Check.
In this era of big beige clunkers, glowing green type, and rainbow cord-spaghetti were the seeds of the world we know and love. And love to hate.
February 26, 2017
This book was a great read from start to finish. It takes you through the journey that an engineering in the 70s went through to get a machine to market. Tracy Kidder writes it in a way that such a dry subject reads like an epic adventure, describing the engineers with so much detail that they feel like the heroes of said adventure. I think what I personally appreciated the most is that it's also a very good time capsule of the computer industry of the late 70s, showing what has changed, but even more so, how much stayed the same. Further more, it's a very interesting case study in how to manage engineers, seeing how much the team was willing to sacrifice just because they got so much freedom and influence in the work they were doing.
I'd say this is a must-read for anyone in the tech industry and a highly recommended read even for those outside of it.
I'd say this is a must-read for anyone in the tech industry and a highly recommended read even for those outside of it.
September 4, 2017
Terrific look at a piece of computer history written at the time it was actually happening. I'd just read Tracey Kidder's book about writing and as a fan of computer history thought this would be a good read. It was as a team puts together Data Generals first 32 bit minicomputer. I'd recommend this book to anyone that enjoys computer history. Well written and fast paced.
January 23, 2019
This book spoke to me right from the intro.
"[The book's title implies] something about the collective character and effort of a group of people who worked only party for their pay, most of them reveling in the difficulty of their circumstances and the complexity of their task, to create something that they knew was transitory. As Camus said of Sisyphus, one must imagine them happy."
"[The book's title implies] something about the collective character and effort of a group of people who worked only party for their pay, most of them reveling in the difficulty of their circumstances and the complexity of their task, to create something that they knew was transitory. As Camus said of Sisyphus, one must imagine them happy."
May 18, 2010
About 6 years ago, a sort of scandal rocked the gaming industry related to a blog post by a woman known as "EASpouse". The blog post criticized EA's labor practices at the time, which required employees to work massive amounts of unpaid overtime, as they were salaried employees. By massive, I mean about 12-16 hour days, 6 days a week, regularly. This was a big deal among gamers, because very few of us had ever had the opportunity to peek behind the curtain like this. It was likely that most of us viewed game development with a variation of the way that Roald Dahl as a child imagined the inside of the Cadbury Chocolate Factory near the boarding school he attended (which later led to Charlie & the Chocolate Factory).
The Soul of a New Machine, by Tracy Kidder shows that such working conditions are nothing new. The book follows the development process of Data General's micro-computer (sort of like a rack mounted server, except it's the size of the whole unit, but essentially only being one of the server nodes), that would be a successor to their Eclipse line of microcomputers, code named the Eagle, and later released as the MV/8000. The book goes into both the personal and technical aspects of the development process, profiling the various men (and a few women) involved in the project, and giving a description of the technical aspects of the process for the layman.
While the technical bits (pardon the pun), are enjoyable, the book's strength, and where it spends most of its time, is in profiles of the people. The book paints a bleak picture of the inner workings of Data General. The working conditions at Data General, particularly on this project, are brutal. Much as with EA Spouse, employees are salaried, with no overtime pay, and work 12-16 hour days, 6 days a week. As the project goes on, project leads and younger employees are worn down. Often, employees at Data General observe that the company brings in a lot of new fresh recruits, and few stay at the company after they turn 30. Many of these new recruits drop out for various reasons, and often employees discuss the company's sweat-shop like working conditions. As the project moves into the heat of summer, the air conditioning breaks, turning their windowless basement office into a sweltering oven, which they can't even leave the door open for, for security reasons. Only after the employees strike do they fix the air conditioning.
By the end of the book, several of the project leads, themselves burned out, leave the company, and while some of the employees on the Eagle team stay on, many more have left.
Tracy Kidder got an impressive amount of access at Data General when he wrote this book, and while he's honest and truthful about what happened there, Data General, at least to my 21st century mind, comes out of this book smelling like shit. I base this solely on what Data General does, and I know this because Kidder doesn't whitewash - he thankfully calls it right down the middle.
While the book is never accusatory, it makes clear that Data General is a predatory employer. It preys on young, semi-idealistic college Engineering graduates, who don't have a lot of job experience and are looking more for interesting problems to solve, interesting work to do, than a big paycheck. They promise them interesting problems, and briefly, very briefly, warn them that there will be long hours and possibly a limited social life, that this job will become their life. To meet the deadlines required of them they will have to give up friends, family, and the outside world, living only the job, for months or years at a time. Plus, because they're salaried, despite all the hours they get that would be overtime, they're only making their standard pay grade.
It chews up 22-24 year old kids, and spits them out at 30, burnouts who had great potential, but were consumed by their jobs. They don't say if many of these former employees stay in the industry, and some certainly do - Ray Ozzie, creator of Lotus Notes and current Chief Software Architect at Microsoft is a Data General veteran. However, those who leave the industry with a sour taste in their mouth will probably leave worse off then they would be if they worked somewhere else. Had they been actually paid overtime, they could have possibly built a nest egg that could have allowed them to retire early, or to at least take their time looking for work elsewhere.
While some poor decisions related to processor architecture helped to kill Data General right before the dawn of the 21st century, it is my suspicion that the boom in Silicon Valley may have inspired a brain drain. Nicer weather, a less oppressive corporate culture. For people who wanted more money, there was the change to come in on the ground floor of companies which had the potential to be worth millions and get significant stock options. For those who preferred challenge, they could face whole new challenges when designing new systems and new architectures at the new companies in the Valley.
In summary, the book is a high resolution snapshot of the early days of the computer industry, before the internet started to permeate our lives in subtle ways - computerized tax processing, credit cards, ATM machines, and so on, leading up to the more overt ways it would later find its way in - Bulletin Board Services, E-Mail, and finally, proper web pages. People interested in the history of the computer industry will certainly find this fascinating. People who don't care about the history of computing can still find something in the profiles of the people in this project, and how the project's process slowly wears them all down.
The Soul of a New Machine, by Tracy Kidder shows that such working conditions are nothing new. The book follows the development process of Data General's micro-computer (sort of like a rack mounted server, except it's the size of the whole unit, but essentially only being one of the server nodes), that would be a successor to their Eclipse line of microcomputers, code named the Eagle, and later released as the MV/8000. The book goes into both the personal and technical aspects of the development process, profiling the various men (and a few women) involved in the project, and giving a description of the technical aspects of the process for the layman.
While the technical bits (pardon the pun), are enjoyable, the book's strength, and where it spends most of its time, is in profiles of the people. The book paints a bleak picture of the inner workings of Data General. The working conditions at Data General, particularly on this project, are brutal. Much as with EA Spouse, employees are salaried, with no overtime pay, and work 12-16 hour days, 6 days a week. As the project goes on, project leads and younger employees are worn down. Often, employees at Data General observe that the company brings in a lot of new fresh recruits, and few stay at the company after they turn 30. Many of these new recruits drop out for various reasons, and often employees discuss the company's sweat-shop like working conditions. As the project moves into the heat of summer, the air conditioning breaks, turning their windowless basement office into a sweltering oven, which they can't even leave the door open for, for security reasons. Only after the employees strike do they fix the air conditioning.
By the end of the book, several of the project leads, themselves burned out, leave the company, and while some of the employees on the Eagle team stay on, many more have left.
Tracy Kidder got an impressive amount of access at Data General when he wrote this book, and while he's honest and truthful about what happened there, Data General, at least to my 21st century mind, comes out of this book smelling like shit. I base this solely on what Data General does, and I know this because Kidder doesn't whitewash - he thankfully calls it right down the middle.
While the book is never accusatory, it makes clear that Data General is a predatory employer. It preys on young, semi-idealistic college Engineering graduates, who don't have a lot of job experience and are looking more for interesting problems to solve, interesting work to do, than a big paycheck. They promise them interesting problems, and briefly, very briefly, warn them that there will be long hours and possibly a limited social life, that this job will become their life. To meet the deadlines required of them they will have to give up friends, family, and the outside world, living only the job, for months or years at a time. Plus, because they're salaried, despite all the hours they get that would be overtime, they're only making their standard pay grade.
It chews up 22-24 year old kids, and spits them out at 30, burnouts who had great potential, but were consumed by their jobs. They don't say if many of these former employees stay in the industry, and some certainly do - Ray Ozzie, creator of Lotus Notes and current Chief Software Architect at Microsoft is a Data General veteran. However, those who leave the industry with a sour taste in their mouth will probably leave worse off then they would be if they worked somewhere else. Had they been actually paid overtime, they could have possibly built a nest egg that could have allowed them to retire early, or to at least take their time looking for work elsewhere.
While some poor decisions related to processor architecture helped to kill Data General right before the dawn of the 21st century, it is my suspicion that the boom in Silicon Valley may have inspired a brain drain. Nicer weather, a less oppressive corporate culture. For people who wanted more money, there was the change to come in on the ground floor of companies which had the potential to be worth millions and get significant stock options. For those who preferred challenge, they could face whole new challenges when designing new systems and new architectures at the new companies in the Valley.
In summary, the book is a high resolution snapshot of the early days of the computer industry, before the internet started to permeate our lives in subtle ways - computerized tax processing, credit cards, ATM machines, and so on, leading up to the more overt ways it would later find its way in - Bulletin Board Services, E-Mail, and finally, proper web pages. People interested in the history of the computer industry will certainly find this fascinating. People who don't care about the history of computing can still find something in the profiles of the people in this project, and how the project's process slowly wears them all down.
June 13, 2017
They were building temples to God. It was the sort of work that gave meaning to life. That's what West and his team of engineers were looking for, I think.
An incredible account of what it feels like to work in the computer industry, an accurate description of computer architecture (that is still relevant today), and an all-around amazing book. Touches many aspects of hardware, management and the emotional intricacies of engineering.
On a personal note, to me, it captures the essence of computers and the people who make them. This was a very special read to me as a computer engineering undergraduate - a fantastic accomplishment that someone from a different field of expertise managed to grasp in such a beautiful way the art of the machine and the people working at the forefront of its development. I had a feeling from the first page, that I was going to like this book. It did not disappoint.
"The game of programming - and it is a game - was so fascinating. We'd stay up all night and experience it. It really is like a drug, I think."
Sounds about right.
October 8, 2011
Some comments in lieu of a review:
Anyone interested in the characters presented in this remarkable, Pulitzer-winning book by Tracy Kidder should consider reading a follow-up published by Wired in 2000…
Some more recent readers appear to have found the book "dated" in one way or another, a historical relic of the late 1970s. Granted, the products of computer technology have vastly changed. But the processes by which computer technology is developed may not have changed so much, if at all, and in any case have probably varied with time and context. Anyone lucky enough to get a job with Google nowadays won't find much in this book to remind them of work, but some smaller and/or hungrier companies still operated this way in the 90s, when I worked at a few, and surely some still do…
Anyone interested in the characters presented in this remarkable, Pulitzer-winning book by Tracy Kidder should consider reading a follow-up published by Wired in 2000…
Some more recent readers appear to have found the book "dated" in one way or another, a historical relic of the late 1970s. Granted, the products of computer technology have vastly changed. But the processes by which computer technology is developed may not have changed so much, if at all, and in any case have probably varied with time and context. Anyone lucky enough to get a job with Google nowadays won't find much in this book to remind them of work, but some smaller and/or hungrier companies still operated this way in the 90s, when I worked at a few, and surely some still do…
September 11, 2015
This was a fantastic read. Tracy Kidder captures a period in computing history that I'd only ever vaguely heard about. The race to build (or in this case retrofit) the first 32-bit microcomputers!
This a fundamentally human exploration of how to inspire and lead people to tilt at windmills. You see how technical credibility is earned, and how teams come to inhabit a realm of their own as they approach launch.
Lots of crazy debugging stories, some fantastic character sketches make a book that is well worth your time.
This a fundamentally human exploration of how to inspire and lead people to tilt at windmills. You see how technical credibility is earned, and how teams come to inhabit a realm of their own as they approach launch.
Lots of crazy debugging stories, some fantastic character sketches make a book that is well worth your time.
June 18, 2018
A very nice story of how a small team of engineers works to create a new computer for Data General in the late 1970s. The computer is not particularly groundbreaking, a new 32-bit computer that is software-compatible with the old 16-bit model. But the story is remarkable for its insights into how the work got done. It explains the characters, their motivations, some technical details (at just the right detail)—and is filled with memorable and realistic anecdotes. It is well paced, well written and well organized, a very nice piece of sociology.
July 1, 2015
I read this many years ago and many books ago. But it made a big impression on my younger self about the quest for something bigger than yourself. You don't do something for money or glory, you do it for the deep internal feeling of accomplishment.
February 19, 2019
There are many, many project management books that purport to reveal the ultimate system for surmounting the myriad challenges to releasing a product on-time, in-budget, and with all the promised features. It's a popular and useful genre, even if much of the material is just reshuffled and rebranded old bromides, but sometimes the most helpful and memorable way to offer project management advice is to just pick a single case study and dive in deep to explore the group dynamics that result - or don't - in a successful product. I'd previously read Mountains Beyond Mountains, Kidder's excellent profile of Dr. Paul Farmer, and this much earlier work, which won him a Pulitzer, is just as detailed, thoughtful, and revealing. It's about the race from 1978 to 1980 by one team of computer engineers at Data General to develop and release a 32-bit "minicomputer" (one of the many charmingly antiquated terms that will give those who know their industry history a smile) called the Eclipse in competition with another, more-prestigious team that's been given a more glamorous project in a shiny new office, with the fate of the company looming in the background. Heroes and villains are the keys to great drama, and so as the narrative follows the protagonists, who are working on "Eagle", a 32-bit extension of the existing 16-bit line of computer hardware instead of the brand-new computer of their dreams that they imagine their counterparts are gleefully assembling, their struggles to design, build, test, debug, and actually finish a computer without more hacks, kludges, and shortcuts than are absolutely unavoidable in such a short time take on a mythic glow that anyone working on a big project in the tech industry under a tight deadline will immediately recognize, despite the passage of nearly 40 years.
If I had to pick a single part of the book that best-represents why the book would make a worthy addition to a computer engineering syllabus, it would be the chapter "The Case of the Missing NAND Gate". It's an almost self-contained episode towards the end of the book, where, late in the development cycle, several engineers are attempting to debug an erratic logic failure, which occurs just often enough to be indicative of a real problem but not so often as to be easily reproducible. Kidder relays the team's efforts to determine if this diagnostic failure is at root a software or a hardware issue, with an amusing layer of "antagonistic camaraderie" on top of their troubleshooting, as all of them had a hand in designing the machine and each wants to solve the problem but none wants to have the root cause bear their fingerprints. This was back in the era when computer design involved the frequent use of oscilloscopes and it was often a genuine question if chips on a board weren't properly spaced for optimal signal timing, so fans of vintage computing will really enjoy as Kidder walks the reader through the finer points of system caches, assembly microcode, page faults, and logic gates while various engineers, working in shifts, propose and reject theories to explain the anomaly. It's a genuine puzzle, and Kidder does a great job explaining just what the problem is and why it's so difficult to diagnose and eventually solve, translating the arcane technical details of the fault with the various components of the system architecture until it's not just lucid but even enthralling. Here's his rendition of one potential explanation from one engineer named Guyer:
"The diagnostic program originally puts the target instruction at address 21765, and then, sometime later on, it moves the target instruction to 21766. But the IP never gets word of the change, though the System Cache does. Now, sometime after the target instruction is switched from mailbox 21765 to 21766, the program directs Gollum to execute the instruction at 21766. The IP receives this command and looks through its cache. It says to itself, in effect, 'Mailbox 21766? I've got that address and there's an instruction in it. Let's run it.' But in the I-cache, the target instruction is still at 21765, and mailbox number 21766 contains an error message. In short, the I-cache contains an outdated piece of memory. Why didn't it get updated along with the other parts of the memory system? Maybe, Guyer writes, the System Cache is to blame. The System Cache is supposed to know exactly what is in the I-cache. If an instruction or data gets moved to a new address, the System Cache is supposed to tell the IP to throw away the outdated mailbox and get the new one, the one with the target instruction in it. Somewhere back in the program, Guyer figures, the System Cache lost track of what was in the I-cache. It forgot that the IP had the target instruction in mailbox 21765, and so, when the change was made in the location of the target instruction, it never told the IP to get rid of the old, outdated mailbox. Guyer likes this hypothesis. He records it with mounting enthusiasm; and describing it later, he repossesses the feeling, speaking rapidly, gesturing with both hands. Then he stops, puts his hands on the table, and says, 'Of course, it was completely wrong.'"
The book is also notable for broader reasons. Massachusetts was a much larger center of the technology industry in the 1970s and 80s than it is today, and the "Route 128" cluster competed directly with Silicon Valley for talent and prestige. However, the Eclipse team's main antagonists were not in California but in North Carolina, giving the modern reader a glimpse of the "flight to the Sunbelt" in embryo that has helped the Research Triangle, among other places, at Massachusetts' relative expense. Data General was founded by former employees of Digital Equipment Corporation; I've read articles arguing that Massachusetts' relatively strict enforcement of noncompete agreements was a major force that drove tech firms to less strict jurisdictions, but that doesn't seem to have been as large an issue here as the typical lure of lower taxes. However, prospective MBAs should scrutinize closely the decision by corporate management to have two different teams working on overlapping products, as ultimately the highly-regarded North Carolina team working on the prestigious brand-new 32-bit machine (dubbed "the Fountainhead Project", with hilarious irony) was upstaged by the "Eagle" team, whose less-ambitious 32-bit extension of the 16-bit Eclipse became a huge moneymaker for the company. Now, hindsight is 20/20, and it's obviously impossible to consistently tell ex ante if internal competition, which is often positive, will in the end have wasted resources. After all, the Eagle team did produce an extremely successful product, although we don't know how much was spent on the Fountainhead team. But lack of clear focus is always risky, and corporate politics can have damaging downstream effects on teams of even very smart people.
But any look into the subtleties of nerd psychology has to account for the fact that the drive to create cool technology is often far more powerful than any corporate folly, even and perhaps especially if that involves extremely long hours of hard work. Occasionally the concept of "mushroom management" is invoked, which turns out to mean "put 'em in the dark, feed 'em shit, and watch 'em grow", and one paradoxical upside of not being the top brass' favorite project is that, with protective leadership, that can actually mean more opportunity to produce. There's an interesting detail in the life story of Tom West, the top manager for the Eagle project: "He went to Amherst College, in western Massachusetts, where he studied the natural sciences. He did so without academic distinction, and it happened that Amherst was just then embracing a new Calvinist fad called the underachiever program: young men whose brains seemed much better than their grades were expelled for a year, so that they might improve their characters. At Amherst, certainly, and possibly in the entire nation, West became the first officially branded underachiever. It was something he'd always remember." This story takes place after the end of the naive cyberhippie movement of the Whole Earth Catalog/"All watched over by machines of loving grace" era, so that technoromance had been firmly replaced by a more modern engineering sensibility, but there's still poignancy of the ceremony at the end of the project, where the team members come to grips with how much of themselves they've put into what would be released as the Data General Eclipse MV/8000, elevates what could have been just an unusually lengthy product diary into an account of creation that justly deserved its Pulitzer. One of the engineers had a typical complaint:
"What a way to design a computer! 'There's no grand design,' thinks Rosen. 'People are just reaching out in the dark, touching hands.' Rosen is having some problems with his own piece of the design. He knows he can solve them, if he's just given the time. But the managers keep saying, 'There's no time.' Okay, Sure. It's a rush job. But this is ridiculous. No one seems to be in control; nothing's ever explained. Foul up, however, and the managers come at you from all sides. 'The whole management structure,' said Rosen. 'Anyone in Harvard Business School would have barfed.'"
Maybe, but the reason why his project shipped and his rival's didn't wasn't because he had superior consultants from Harvard. As Kidder recounts from attending a trade conference: "It seemed to me that computers have been used in ways that are salutary, in ways that are dangerous, banal and cruel, and in ways that seem harmless if a little silly. But what fun making them can be!"
If I had to pick a single part of the book that best-represents why the book would make a worthy addition to a computer engineering syllabus, it would be the chapter "The Case of the Missing NAND Gate". It's an almost self-contained episode towards the end of the book, where, late in the development cycle, several engineers are attempting to debug an erratic logic failure, which occurs just often enough to be indicative of a real problem but not so often as to be easily reproducible. Kidder relays the team's efforts to determine if this diagnostic failure is at root a software or a hardware issue, with an amusing layer of "antagonistic camaraderie" on top of their troubleshooting, as all of them had a hand in designing the machine and each wants to solve the problem but none wants to have the root cause bear their fingerprints. This was back in the era when computer design involved the frequent use of oscilloscopes and it was often a genuine question if chips on a board weren't properly spaced for optimal signal timing, so fans of vintage computing will really enjoy as Kidder walks the reader through the finer points of system caches, assembly microcode, page faults, and logic gates while various engineers, working in shifts, propose and reject theories to explain the anomaly. It's a genuine puzzle, and Kidder does a great job explaining just what the problem is and why it's so difficult to diagnose and eventually solve, translating the arcane technical details of the fault with the various components of the system architecture until it's not just lucid but even enthralling. Here's his rendition of one potential explanation from one engineer named Guyer:
"The diagnostic program originally puts the target instruction at address 21765, and then, sometime later on, it moves the target instruction to 21766. But the IP never gets word of the change, though the System Cache does. Now, sometime after the target instruction is switched from mailbox 21765 to 21766, the program directs Gollum to execute the instruction at 21766. The IP receives this command and looks through its cache. It says to itself, in effect, 'Mailbox 21766? I've got that address and there's an instruction in it. Let's run it.' But in the I-cache, the target instruction is still at 21765, and mailbox number 21766 contains an error message. In short, the I-cache contains an outdated piece of memory. Why didn't it get updated along with the other parts of the memory system? Maybe, Guyer writes, the System Cache is to blame. The System Cache is supposed to know exactly what is in the I-cache. If an instruction or data gets moved to a new address, the System Cache is supposed to tell the IP to throw away the outdated mailbox and get the new one, the one with the target instruction in it. Somewhere back in the program, Guyer figures, the System Cache lost track of what was in the I-cache. It forgot that the IP had the target instruction in mailbox 21765, and so, when the change was made in the location of the target instruction, it never told the IP to get rid of the old, outdated mailbox. Guyer likes this hypothesis. He records it with mounting enthusiasm; and describing it later, he repossesses the feeling, speaking rapidly, gesturing with both hands. Then he stops, puts his hands on the table, and says, 'Of course, it was completely wrong.'"
The book is also notable for broader reasons. Massachusetts was a much larger center of the technology industry in the 1970s and 80s than it is today, and the "Route 128" cluster competed directly with Silicon Valley for talent and prestige. However, the Eclipse team's main antagonists were not in California but in North Carolina, giving the modern reader a glimpse of the "flight to the Sunbelt" in embryo that has helped the Research Triangle, among other places, at Massachusetts' relative expense. Data General was founded by former employees of Digital Equipment Corporation; I've read articles arguing that Massachusetts' relatively strict enforcement of noncompete agreements was a major force that drove tech firms to less strict jurisdictions, but that doesn't seem to have been as large an issue here as the typical lure of lower taxes. However, prospective MBAs should scrutinize closely the decision by corporate management to have two different teams working on overlapping products, as ultimately the highly-regarded North Carolina team working on the prestigious brand-new 32-bit machine (dubbed "the Fountainhead Project", with hilarious irony) was upstaged by the "Eagle" team, whose less-ambitious 32-bit extension of the 16-bit Eclipse became a huge moneymaker for the company. Now, hindsight is 20/20, and it's obviously impossible to consistently tell ex ante if internal competition, which is often positive, will in the end have wasted resources. After all, the Eagle team did produce an extremely successful product, although we don't know how much was spent on the Fountainhead team. But lack of clear focus is always risky, and corporate politics can have damaging downstream effects on teams of even very smart people.
But any look into the subtleties of nerd psychology has to account for the fact that the drive to create cool technology is often far more powerful than any corporate folly, even and perhaps especially if that involves extremely long hours of hard work. Occasionally the concept of "mushroom management" is invoked, which turns out to mean "put 'em in the dark, feed 'em shit, and watch 'em grow", and one paradoxical upside of not being the top brass' favorite project is that, with protective leadership, that can actually mean more opportunity to produce. There's an interesting detail in the life story of Tom West, the top manager for the Eagle project: "He went to Amherst College, in western Massachusetts, where he studied the natural sciences. He did so without academic distinction, and it happened that Amherst was just then embracing a new Calvinist fad called the underachiever program: young men whose brains seemed much better than their grades were expelled for a year, so that they might improve their characters. At Amherst, certainly, and possibly in the entire nation, West became the first officially branded underachiever. It was something he'd always remember." This story takes place after the end of the naive cyberhippie movement of the Whole Earth Catalog/"All watched over by machines of loving grace" era, so that technoromance had been firmly replaced by a more modern engineering sensibility, but there's still poignancy of the ceremony at the end of the project, where the team members come to grips with how much of themselves they've put into what would be released as the Data General Eclipse MV/8000, elevates what could have been just an unusually lengthy product diary into an account of creation that justly deserved its Pulitzer. One of the engineers had a typical complaint:
"What a way to design a computer! 'There's no grand design,' thinks Rosen. 'People are just reaching out in the dark, touching hands.' Rosen is having some problems with his own piece of the design. He knows he can solve them, if he's just given the time. But the managers keep saying, 'There's no time.' Okay, Sure. It's a rush job. But this is ridiculous. No one seems to be in control; nothing's ever explained. Foul up, however, and the managers come at you from all sides. 'The whole management structure,' said Rosen. 'Anyone in Harvard Business School would have barfed.'"
Maybe, but the reason why his project shipped and his rival's didn't wasn't because he had superior consultants from Harvard. As Kidder recounts from attending a trade conference: "It seemed to me that computers have been used in ways that are salutary, in ways that are dangerous, banal and cruel, and in ways that seem harmless if a little silly. But what fun making them can be!"
August 12, 2021
I will put in a placeholder review for this amazing book for now. I wish I read this book when I was in college (2013), instead, I was learning about 8085 microcontroller which was also developed in 1981! Think of reading about an outdated chip in a dry format when I could have been reading about how computers are made. As a software engineer, I have taken it for granted the very machine which runs my code. Always power-hungry, I shift from a 16gb machine to 32gb machine without giving a second thought.
This book tells a story about the development of a "secret" machine developed in the span of one and half years. Built by a team comprising mostly of college graduates, along with some industry veterans, you will learn about the tradeoffs and some ingenious ideas employed to release the machine in such a short duration. The author explains technical terms in such a way that no previous hardware knowledge is required. Recommended for engineers of any domain (especially hardware/software)
This book tells a story about the development of a "secret" machine developed in the span of one and half years. Built by a team comprising mostly of college graduates, along with some industry veterans, you will learn about the tradeoffs and some ingenious ideas employed to release the machine in such a short duration. The author explains technical terms in such a way that no previous hardware knowledge is required. Recommended for engineers of any domain (especially hardware/software)
November 19, 2020
This book is simply great. It captures working at a technology company: the long hours, no overtime, working for passion remarkably well. At the same time, it captures leadership and what effective leadership could look like without taking the credit for it.
Displaying 1 - 30 of 707 reviews