Computers have changed since 1981, when Tracy Kidder memorably recorded the drama, comedy, and excitement of one company's efforts to bring a new microcomputer to market. What has not changed is the feverish pace of the high-tech industry, the go-for-broke approach to business that has caused so many computer companies to win big (or go belly up), and the cult of pursuing mind-bending technological innovations. The Soul of a New Machine is an essential chapter in the history of the machine that revolutionized the world in the 20th century.
©2011 Tracy Kidder (P)2016 Hachette Audio
I read this book shortly after it was published, and have re-read it every few years since. In fact, it was the first Kindle book I purchased. So I was really excited to get it as an audiobook. Unfortunately, I was a little bit disappointed.
Let's start with the story itself: It is definitely a bit of a hagiography to the 32-bit Eclipse team at Data General. While the author tries to tell the story in an unbiased way, nowhere in the book is it mentioned that Tracy Kidder was college roommate's with Tom West, which is how he came to be writing that story. Still, all of that being said, Mr. Kidder does an excellent job of explaining the technical issues clearly to an educated layman. As a long time professional software developer myself, I must credit him for (for example) his terrific explanation of double-page faults. He definitely took the time to get the technical details simplified but correct. So from the point of view of content, the book is a good read, whether in dead tree form, Kindle ebook, or audiobook.
However, the audiobook performance leaves some things to be desired. For example, the reader has clearly never heard certain words pronounced correctly, and rather than looking them up, guessed, and guessed wrong. Two in particular are "adjutant" and "wan." When a reader mispronounces a word, it yanks me out of the flow, hard. So a note to readers: If you are doing either a technical non-fiction book, or a science-fiction/fantasy book, grab a dictionary, and look up any word you don't personally know and use on a daily basis. These kinds of books tend to use a lot more uncommon English words, and the listeners tend to know those words and use them, themselves. So hearing the reader get it wrong really spoils the listen.
Second, the reader really didn't do any voice characterisations. I know that it's harder when these are real people, not characters. But many of the people have their voices described well enough that a good reader could get close enough to how they should sound. Instead, the reader just read it. And barring the vocabulary problems mentioned above, he did an okay job. But okay isn't what I've come to expect from audiobooks here. I've heard a number of books where, after listening, I thought, "This is what those characters sound like." This read could almost have been done by a decent TTS system. So paying good money for a mediocre reading smarts.
Any road, if you are old enough to remember the mini-computer and personal computer revolutions, this book will be quite nostalgic. And if you are too young to remember, you might find this an interesting insight into the industry. Honestly, the working environment at Data General on the 32-bit Eclipse project will seem very familiar to anyone who has worked in a startup, or for a high-company that is still run like a startup (I'm looking at you, Amazon). So I would recommend it over all, but bear in my objections and you'll hear a great story, well written, if only averagely well read.
I found this book fascinating when I first read it years ago and still do. It does an excellent job of conveying the excitement of building one of the first computers and explains the nuts and bolts for the general reader. I loved the book, but for a few readers it could get a little slow toward the end so I’m rating it a four
A classic story about what a small team of motivated kids can accomplish against an impossible schedule. The project leader Tom West didn't want to hear how long it would take, as that would invite fudge factoring. So he turned it around: "what's the earliest date you can't prove you won't be finished by?" Then he would ask them to "sign up" to get close to that date.
The reader is terrific , though he thinks kluge rhymes with fudge -- but he's not the only one.
Read this book back in the mid-80's. Completely changed my view of part of of the world I was heading into as a software developer. Great to hear it instead of just read it! Thanks Audible for getting this title !
Report Inappropriate Content