Long time lurker, first time poster.
Another take on the Rambus thing...It's agreed that a big black eye goes to Intel because it was their people responsible for the incorrect motherboard design. A serious flaw in their QA department, to say the least. But, in spite of all Intel's mistakes, I bet the whole situation could still have been avoided if Rambus had provided the INTC installation team with competent project management, or at least a competent project manager. And you can bet that the INTC management team has let Rambus know that, while Rambus may not have failed here, they were in a position to make the transition easier and they didn't. There will be some sacrificial lambs...on both sides. A gorilla develops in part because of good management, and this time Rambus missed the mark in that department. I freely admit that I know nothing about RMBS' management, and I wouldn't be screaming for their heads (yet) if I was a shareholder because maybe this is just a growing pain. If nothing else, this is an opportunity for them to learn and possibly take a step from gorilla wannabee to the real thing.
Another thought is that the manual states that one difference between a gorilla and a king is the fact that execution is not always crucial for a gorilla, but a king's management must always execute. I would be interested to see what others thought about this in the context of the Rambus news. If Rambus' value chain grows in the face of recent developments, does that put them in the jungle instead of the castle? Perhaps that has already been decided by the thread - if so, this event underscores what the manual says.
Swing away,
Rick |
