tag:blogger.com,1999:blog-28344720.post247970601305755504..comments2024-02-21T06:47:29.430-07:00Comments on Chip Overclock<sup><small>®</small></sup>: Dead Man WalkingChip Overclockhttp://www.blogger.com/profile/11195242013008369733noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-28344720.post-68165422538392595512012-12-21T10:49:03.152-07:002012-12-21T10:49:03.152-07:00I apologize if I gave the impression that I was tr...I apologize if I gave the impression that I was trying to deflect the blame for this fiasco from myself. Quite the contrary. In complex situations like this, there is always plenty of blame to go around. Like most catastrophes, there are multiple causes that all line up to allow it to happen; if that weren't the case, existing processes would have prevented the catastrophe in the first place.Chip Overclockhttps://www.blogger.com/profile/11195242013008369733noreply@blogger.comtag:blogger.com,1999:blog-28344720.post-4117976187172394532012-12-21T10:36:24.489-07:002012-12-21T10:36:24.489-07:00A case of shoot the messenger? Typical management...A case of shoot the messenger? Typical management solution, blame everyone else but yourself. After all you were neither responsible for the lack of bug fixes in the development version, nor for the inability of the relevant parts of the organization to communicate.Craig Ruffnoreply@blogger.com