|
|
|
|
|
by duggan
4121 days ago
|
|
> I can't resist reminding you that 1 command from a sysadmin routing traffic to the wrong network was the cause of the last major outage there :) If you're going to bring that up, I can't resist reminding you of that time you had poor sysadmins running up and down stairs with buckets of fuel to keep your servers running[1]. > I've always said this: the cloud isn't a good fit for us; do what works for you. There are costs. Frankly, it appears Stack Exchange prefers to lay those on its people rather than its purse. [1]: http://blog.stackoverflow.com/2012/11/se-podcast-36-we-got-h... |
|
When your neighbor's house is on fire you don't argue over the price of the hose. You help. Our remote people that couldn't come help in person also helped them replicate their entire network in AWS as a backup plan.
I don't usually post pissed off comments, but you're dead wrong here and intetionally or not demeaning a good company and good people whom, because they cared, came to help in a time of emergency. I take it you weren't in New York during Sandy; it looked like a post-apocalyptic war zone afterwards.
TL;DR - You don't know what you're talking about.