- Tapa dura: 240 páginas
- Editor: Citadel Press Inc.,U.S. (5 de febrero de 2009)
- Idioma: Inglés
- ISBN-10: 0806531010
- ISBN-13: 978-0806531014
- Valoración media de los clientes: Sé el primero en opinar sobre este producto
Clasificación en los más vendidos de Amazon:
nº729.643 en Libros en idiomas extranjeros (Ver el Top 100 en Libros en idiomas extranjeros)
- n.° 1436 en Libros en idiomas extranjeros > Ciencias, tecnología y medicina > Tecnología e ingeniería > Tecnologías energéticas > Ingeniería eléctrica
- n.° 2738 en Libros en idiomas extranjeros > Informática, internet y medios digitales > Guías de videojuegos y juegos para PC
- n.° 12661 en Libros en idiomas extranjeros > Informática, internet y medios digitales > Programación y desarrollo de software
The Race For A New Game Machine: Creating the Chips Inside the Xbox 360 & the Playstation 3: Creating the Chips Inside the Xbox 360 and the Playstation 3 (Inglés) Tapa dura – 5 feb 2009
Los clientes que compraron este producto también compraron
Descripción del producto
Reseña del editor
A personal account of the author's leadership of the team that created a revolutionary microprocessor that changed personal computers and the gaming industry.
No es necesario ningún dispositivo Kindle. Descárgate una de las apps de Kindle gratuitas para comenzar a leer libros Kindle en tu smartphone, tablet u ordenador.
Obtén la app gratuita:
Detalles del producto
Si eres el vendedor de este producto, ¿te gustaría sugerir ciertos cambios a través del servicio de atención al vendedor?
Opiniones de clientes
|5 estrellas (0%)|
|4 estrellas (0%)|
|3 estrellas (0%)|
|2 estrellas (0%)|
|1 estrella (0%)|
Opiniones de clientes más útiles en Amazon.com
The negative reviews about this book are, quite unfortunately, correct. I got this after having read Opening the Xbox, an absolutely fascinating story about the creation of the Xbox platform. Unfortunately, this book doesn't have any of the intrigue that book has.
I want to point out just a few issues that I have with it so that others are aware of it:
1) The author notes in a relatively early chapter that he was not really involved with the gaming industry before getting back into this chip design. All right, fair enough -- but then he says that he studies the history of it and walks the reader through pinball, and arcades, and then gets to the video game crash... And then says that the market was dead until Sony created the Playstation.
Now, unless I'm mistaken, Nintendo was in the middle there somewhere, and Nintendo was actually responsible for getting Sony into the gaming business. And, he mentions Sega, but notes that they made their name with early 80s arcade games.
I don't know if he was trying to say that was the part of the gaming world he followed or not, but it struck me as being extremely out of place. Either finish the story and don't skip 1984-1995, or leave the history to another book.
2) He continually talks about deadlines that are marching closer, but fails to convey the urgency behind these deadlines. I remember a part about halfway through where there was a serious error that was made -- during this explanation, he takes time to explain that there are things that maybe could be done and makes it sound like it isn't horrible, but then talks about how jobs were threatened over this and so on. It's almost jarring to read and to try to flip back and forth with it.
3) The engineers and engineering team seems to be introduced willy-nilly, where you get an intro for someone here, and then that person may or may not ever be introduced again. That's great if you hired engineer X for the project, but if you never mention his or her name again in the book, why should I care? It's like introducing 10 characters at the beginning of a play, but then having the play be just about two people -- it's overly confusing.
It feels like he did this to try to thank the people involved with the creation of the chip, but then he spends other parts of the book seemingly throwing people under the bus, so it's very confusing to know exactly what is going on.
Overall, this book has glaring, glaring issues. When I started reading it, I figured I'd tear through the book in a few days like I do with many video game books that I have picked up. Opening the Xbox I finished in less than 24 hours -- but I'm now about 40 pages from the end of the book and nearly two weeks in. It's frustrating, as it tells a fascinating story that I do want to learn and will finish reading the book to get, but an extra few passes in editing would have done this book a lot of good.
The problem with this book is the tone - the author can't seem to decide if he wants to pitch it as a novel or a non-fiction book, and whether he's aiming at a technical audience or laymen. I understood some of the CPU jargon used only because of my electrical engineering degree, while at times he tried to use comparisons to cartoons like Road Runner to explain complicated concepts. It was very jarring.
It's a shame because this book has a lot of potential and there is a lot of interesting info in it. I think it may have been more successful if the authors had partnered with a journalist to write this. Another good example of a book I read recently that did a better job of capturing the race to market for a complicated technical product was Showstopper, which detailed the creation of Windows NT and is still a fantastic read almost 20 years later.
Yet I only gave it three stars. Why? Because I felt it lacked the depth it needed. It turns itself into a cross between a technical book and a business book, leaving it lacking a bit on each side (particularly the business side.) I think this was likely a deliberate decision, hoping to appeal to a wider audience, particularly us game nerds. That's a weakness, however. There could have been a great deal of discussion, particularly on the business end. Organizational design is touched upon, but done so lightly. Here was a joint venture between IBM, Toshiba and Sony, with Microsoft then butting in. The timetables were tight. So many organizational issues, so much innovation to manage, yet the book deals so little with this, leaving constant questions. This is where I longed for the book to go.
As a bit of history I recommend it. If your work involves any of the companies mentioned above then I recommend the book. If you're hoping to be a leader in video games I recommend this, as it'll be fun to second-guess the decisions made and try to see how your leadership would have worked. If you're looking to learn something, particularly something you can apply to your own unrelted business, I'd say you're wasting time.
I enjoyed this book. But I should have - this is very close to the life I want.