Difference between revisions of "Talk:1097: A Hypochondriac's Nightmare"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
(hbcqCLLZV)
Line 1: Line 1:
'''Please type <nowiki>~~~~</nowiki> at the end of comments to include your signature. Thanks!'''
+
I totally agree with Kudo's to the Rimu Team. It was obuovis from the traffic that you were in the middle of it. I have been more than pleased with the reliability & support from RImuhosting.  Obviously, your team knows what did and did not work on a "black" startup and will work to fix those things.I would suggest giving some consideration to planning client communcations in a disaster situation such as this.  As is always the case when watching disasters from the sidelines, the information never comes often enough or accurately enough.  I became a fan of Twitter for these types of episodes.  It seems that campfire was good but got overloaded?  I guess my biggest suggestion is that some planning should be given to how & what to communicate so that it is a little more structured. A lot of people seemed to be taking your information as absolute (based on Rimu's great support track record). Only to find out that the "7PM ETA" was for power restoration not server restoration which came several hours later. Getting the right information out in the "fog of battle" can make the difference between a minor disaster and a major fiasco.One of the key issues that drew me to Rimu and has kept me here is that the support is up front and does not pull any punches.  I am not suggesting you try to script a disaster. I am suggesting that you plan how information is gathered, verified and distributed. If you can't verify a piece of information but feel it needs to be distributed be clear that the information is tenative, etc.According to the information distributed during the event, Colo4 has installed/rigged a temporary ATS and will need to replace that ATS which means another power outage.  Can we get some updates on when and how long that will be?Is someone doing a root cause analysis to determine what happened with the ATS and what needs to be done to prevent a recurrance?
 
 
*I am not sure that hypochondriac is spelled hypochrondiac. According to the dictionary it is hypochondriac. I wonder if RM will fix this. --[[User:Grep|Grep]] ([[User talk:Grep|talk]])
 
**I think hypochondriac is the right spelling (according to Google and Wikipedia)
 
**Is it possible that the spelling of hypo'''chron'''diac is on purpose?  The timing of the banana and jet engine versus the death mites? [[User:Altor|Altor]] ([[User talk:Altor|talk]]) 12:46, 20 August 2012 (UTC)
 
*** I doubt that it was intended, as I would think there would still be the r in driac. It has not been changed as of now, so I can't be sure. #TEBOWTIME 14:19, 20 August 2012 (UTC)
 
****Corrected to proper spelling by RM as of 9/21/12 <sup>[http://www.xkcd.com/1097/]</sup>Maybe we should as well. --[[User:Shine|Shine]] ([[User talk:Shine|talk]]) 17:32, 21 August 2012 (UTC)
 
***Moved page and 1097 redirect to new spelling...--[[User:Bpothier|B. P.]] ([[User talk:Bpothier|talk]]) 22:40, 21 August 2012 (UTC)
 
 
 
*What are "death mites"?
 
** A {{W|Mite}} is a small arthropod that aren't particularly dangerous to humans, at worst causing allergic reactions. I guess "death mites" is another joke on hypochondriacs. [[User:Buggz|Buggz]] ([[User talk:Buggz|talk]]) 11:11, 21 August 2012 (UTC)
 
 
 
*I feel like a Hypochondriac's nightmare would be dying from a disease that they detected at the earilest stage, but could do absolutely nothing about. #TEBOWTIME 10:33, 20 August 2012 (UTC)
 
 
 
*Don't you think the Title Text is more suggesting that Randal has a rash and he made the comic to calm himself down, but then it turns out that he has death mites in real life?
 
** Using the context clues, it's safe to assume that Cueball is thinking the title-text. #TEBOWTIME 13:24, 20 August 2012 (UTC)
 

Revision as of 23:10, 20 September 2012

I totally agree with Kudo's to the Rimu Team. It was obuovis from the traffic that you were in the middle of it. I have been more than pleased with the reliability & support from RImuhosting. Obviously, your team knows what did and did not work on a "black" startup and will work to fix those things.I would suggest giving some consideration to planning client communcations in a disaster situation such as this. As is always the case when watching disasters from the sidelines, the information never comes often enough or accurately enough. I became a fan of Twitter for these types of episodes. It seems that campfire was good but got overloaded? I guess my biggest suggestion is that some planning should be given to how & what to communicate so that it is a little more structured. A lot of people seemed to be taking your information as absolute (based on Rimu's great support track record). Only to find out that the "7PM ETA" was for power restoration not server restoration which came several hours later. Getting the right information out in the "fog of battle" can make the difference between a minor disaster and a major fiasco.One of the key issues that drew me to Rimu and has kept me here is that the support is up front and does not pull any punches. I am not suggesting you try to script a disaster. I am suggesting that you plan how information is gathered, verified and distributed. If you can't verify a piece of information but feel it needs to be distributed be clear that the information is tenative, etc.According to the information distributed during the event, Colo4 has installed/rigged a temporary ATS and will need to replace that ATS which means another power outage. Can we get some updates on when and how long that will be?Is someone doing a root cause analysis to determine what happened with the ATS and what needs to be done to prevent a recurrance?