THE SOUL OF A NEW MACHINE TRACY KIDDER PDF
The Soul Of A New Machine. Home · The Soul Of A New Machine Author: Tracy Kidder Evolutionary Computation: Toward a New Philosophy of Machine . Editorial Reviews. yazik.info Review. The computer revolution brought with it new methods The Soul of A New Machine - Kindle edition by Tracy Kidder. PDF created with FinePrint pdfFactory trial version yazik.info The Soul of a New Machine. Tracy Kidder. Avon Books. ISBN
|Language:||English, Spanish, French|
|Genre:||Children & Youth|
|ePub File Size:||19.87 MB|
|PDF File Size:||17.40 MB|
|Distribution:||Free* [*Register to download]|
TRACY KIDDER PDF. By saving The Soul Of A New Machine (Modern Library) By Tracy Kidder in the gizmo, the means you read will certainly likewise be much . "The Soul of a New Machine" is a non-fiction book written by Tracy Kidder and published in It chronicles the experiences of a computer. THE SOUL OF A NEW MACHINE. Tracy Kidder. BACK BAY BOOKS. Little, Brown and Company. New York Boston London.
The Soul of a New Machine
Soul is a cut above even most well-written nonfiction, as its Pulitzer Prize attests. As Kidder traces the project from conception through Project MUSE promotes the creation and dissemination of essential humanities and social science resources through collaboration with libraries, publishers, and scholars worldwide.
Paperback Verified download. This book is a non-fiction account of the development of a mini-computer in the s. The book begins by describing the background: Data General, a computer company, has been recently leapfrogged by a competitor who put out a bit mini computer system over their bit system.
To keep up with their major competitor DEC , the company begins a development project for their own bit mini computer.
The company HQ is based in Massachusetts. A major feud begins, but basically the group in North Carolina wins and gets to build the new bit system.
However, the story begins in Massachusetts Tom West, an engineering manager in Massachusetts, manages to convince the management that it would be worthwhile to have a 'back-up' bit computer system, that was perhaps backwards compatible with their old bit systems. It would be a sort of 'insurance' so to speak in case development efforts in North Carolina took too long.
With a handful of experienced engineers as team leaders, he recruits essentially fresh college graduates and works the hell out of them to create a rival bit computer system. Over the course of the book, it becomes apparent that the North Carolina facility - despite having more resources, money, engineers, etc. West's team of new recruits really does need to release their product in order for the company to continue competing in the mini-computer market.
The book is not written so much on the technical details of the project, but rather is more of a 'documentary' of the experience of being on the product development team. The level of detail this book captures, and at each level from West's perspective, the perspective of a number of the fresh college graduates, his experienced Team Leaders who speculated on West's motives in driving everyone so hard, the background situation of the company and management is perfect.
Looking back historically, one could easily just conclude that the Massachusetts team succeeded for all sorts of technical reasons.
Log in to Wiley Online Library
But there were a lot of interesting human reasons for why the project succeeded. For one, the project should have never been started in Massachusetts in the first place. The company management did not seem to have any clear idea of what to put their engineers to work on or even really know what they were working on and a wily manager was able to sneak the project by, masquerading it as something else.
The ridiculous management decisions, the company politics, engineers working insane hours on esoteric problems, the strange culture of engineers, the product launch and general lack of appreciation for the engineer's work afterwards - it's amazingly well captured in this book, and I was surprised at how my current company and previous company experiences relate so strongly to the product development described here.
What I liked most about it, was that a lot of the decisions made by West, the company, etc were highly irrational, if you looked at them from the company perspective. But in reality, for often political reasons, feuds, the strange driven personality of a particular manager, the strange management practices of the CEO, all of these mistakes get made, and yet a bit mini computer gets built and saves the company in the end anyway.
It's a great book because it is all true. I am not sure how interesting this would be for someone that doesn't work in product development, but for me, I see this mistakes made in my company every day. It's amazing how much individual personalities, and strange coincidences can drive a project.
An additional tidbit, Wired magazine did a follow up with all of the engineers years after this book was written: A great book. This book should be on the desk of every manager of technical projects in the US.
More than any other work in history, it shows how innovation occurs, and how a few near-genius and hard-working individuals can get things done. It also shows modern organizational theory to be badly flawed, and that the much vaunted group-dynamics and teamwork cannot replace a few bright minds who are dedicated to inventing a new product. The Apple Computer is an example of the concept I'm describing: Steve Wozniac invented the Apple in his garage, and Steve Jobs marketed it.
Amazing, isn't it -- one man essentially created the personal computer all by himself. All alone, not even with a team made of diverse talents and representing various viewpoints. All they do is create kludges that require incessant maintenance and updates. Sound familiar?
See a Problem?
One person found this helpful. Kindle Edition Verified download. I read this Pol based on few recommendations, it took me a while to finish it though. I find certain part of the book to detailed and boring eventually I had to put effort t finish it all.
I cannot say it is bad written, on the contrary it reads well however the subject and the way to tell the story is not my way. Overall a classical book strongly recommended if you are a manager as it explains how to build a group of achiever and potentially shows the aftermath of great success. A bunch of people haphazardly come together to build a new computer and with trust from their managers and earnest desire to excel in their craft manage to bring the damn thing to life.
I personally found this relatable on so many levels; not only the pastiche of people working on the project but also the range of company politics and bickering. This book punched me in the stomach purely from the fact that the project's leader, Tom West, blatantly describes the power of trust to lead teams. Important projects are easy to recruit for.
The Soul of a New Machine
Work runs on peer pressure. Everyone wants to feel an ownership of their project.
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 nev In the early '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.
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.If you would like to authenticate using a different subscribed institution that supports Shibboleth authentication or have your own login and password to Project MUSE.
From Wikipedia, the free encyclopedia. Many of the engineers state that, "They don't work for the money", meaning they work for the challenge of inventing and creating. Anecdotes about this cast of characters are mixed with often detailed but never dull descriptions of the work they did, the result being an almost anthropological analysis of the engineering process that remains a valuable contribution to studies in technology and culture.
DPReview Digital Photography. Write a customer review. Would you like to tell us about a lower price?
- UNLOCKING THE BIBLE DAVID PAWSON PDF
- AKHENATEN HYMN TO THE SUN PDF
- EYE OF THE NEEDLE BOOK
- EYE OF THE WORLD PDF
- THE YOGA BIBLE PDF
- THE WINNERS CRIME EPUB
- JK ROWLING QUIDDITCH THROUGH THE AGES PDF
- URBAN SKETCHING THE COMPLETE GUIDE TO TECHNIQUES PDF
- ANGEL FIRE LA WEATHERLY PDF
- CAPURSO SCIENZA DELLE COSTRUZIONI PDF
- WELCOME STUDENTS BOOK
- CLOSERS SURVIVAL GUIDE PDF
- MS SQL SERVER 2012 EBOOK
- THE DUTIFUL RAKE BY ELIZABETH ROLLS PDF
- HSC TIME TABLE 2016 ARTS PDF