Failure has 1000 reasons, if we have to learn from them there are billion of those...I like to learn from leader's who navigated to sucess...
That is the book of interest to me...
Looking forward to reading anyhow on how to fail and then show how wonderful leadership decios are...only in America.
Ruiz was a disaster both at Motorola and at AMD.
Ruiz squandered AMD's performance advantage, Opteron, and failed to capitalize on Intel's serious missteps (Itanium and Pentium IV) by engaging Intel in a price war despite having the more competitive, premium product line.
Under Ruiz, AMD failed to invest both in mobility and next generation mainstream CPU architectures.
Under Ruiz, AMD wrecked an excellent relationship with its key chipset enabler, Nvidia through AMD's (massively overpriced and mismanaged) acquisition of ATI.
Under Ruiz, AMD failed to secure Apple's PowerPC transition business.
Ruiz was and is deeply despised by most of the technical staff at AMD and Motorola and was subsequently forced to resign, in disgrace, from GlobalFoundries.
To quote one AMD technical staff member:
"If Hector Ruiz ever came back to AMD we'd slash more than just the tires on his car this time"
If that book was published 5 years ago that could had been interesting...but now?...after his Motorola endeavor?? why not write about that experience...AMD fights with Intel are sooo irrelevant today...give me a book on ARM vs Intel, I will read it in a heartbeat
chipmonk, personal attacks and racist remarks are grossly inappropriate in a professional forum.
He certainly must've had logical business reasons for the decisions he made then, most likely with inputs from his Group GMs and mindful of his responsibilities to the CEO and to Motorola stockholders. It didn't work out so well, but after all these years, I think it would be fascinating to get a glimpse of the behind-the-scenes discussions & debates that lead to some of those reorginizations and shifts in strategy.
Hector the Sector Wrector ( as in Motorola Semiconductor Sector ) has the credibility of a Wetback. INCOMPETENT IDIOT who reached the top because of Motorola's disastrous Policy to promote minorities at all costs.
He said AMD got the industry to focus on the consumer. It will be interesting to read his interpretation of that and compare my memories of being a consumer during those days.
In the circles I ran in, it was a "David vs. Goliath" battle. But it was also a battle of focusing on reliability and finish (Intel) vs. focusing on catching by taking shortcuts (AMD).
I understand that both companies likely took shortcuts. Both certainly had misses and hits, but this is the perspective I had.
AMD would skip features like graceful thermal shutdown and allow overclocking to the extreme. Intel would sometimes try to prevent overclocking, ostensibly in the name of reliability, but possibly to protect sales of more expensive chips.
AMD was automatically seen as being better, regardless of any evidence supporting or disputing that position, simply because it was smaller.
Certainly, though, the presence of strong competition kept Intel striving to build better products.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.