on the nature of fuckups. or something.
Mar. 1st, 2009 10:14 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
rmdapparently, i was due for a good solid shoot-yourself-in-the-foot fuckup.
words to the wise from the voice of experience: if you have two devices working as a primary/failover pair, and you want to test them both, you have to test through each of them and not twice through one of them. *facepalm*
*sigh* this is the sort of thing that would've had me wearing the 'bonehead' headpiece when i was at ftp.
on the other hand...
back very shortly after i started at msft, working for the then-fledgling msn, i had an coworker for about 2 months. the guy started, and very shortly after he took another job wrangling networks at some HMO or something. i was told after he left that he apparently thought the stress of working at msft was more than he wanted to deal with.
and i couldn't quite understand this. because at msft, OH MY GOD PEOPLE MIGHT NOT BE ABLE TO READ THEIR EMAIL if there was a fuckup. or, you know, have a fuckup show up above the fold on newspapers all around the world. (yeah, that happened. not my fault, although i did kick myself for not diagnosing and solving it before other people did.) but at an HMO, people might ACTUALLY FUCKING DIE due to information technology fuckups.
words to the wise from the voice of experience: if you have two devices working as a primary/failover pair, and you want to test them both, you have to test through each of them and not twice through one of them. *facepalm*
*sigh* this is the sort of thing that would've had me wearing the 'bonehead' headpiece when i was at ftp.
on the other hand...
back very shortly after i started at msft, working for the then-fledgling msn, i had an coworker for about 2 months. the guy started, and very shortly after he took another job wrangling networks at some HMO or something. i was told after he left that he apparently thought the stress of working at msft was more than he wanted to deal with.
and i couldn't quite understand this. because at msft, OH MY GOD PEOPLE MIGHT NOT BE ABLE TO READ THEIR EMAIL if there was a fuckup. or, you know, have a fuckup show up above the fold on newspapers all around the world. (yeah, that happened. not my fault, although i did kick myself for not diagnosing and solving it before other people did.) but at an HMO, people might ACTUALLY FUCKING DIE due to information technology fuckups.
no subject
Date: 2009-03-01 09:40 pm (UTC)Of course sometimes you're fucked no matter what: Having two separate T3 connections coming into your data room with NIDs located 10 blocks in opposite directions will protect you in a 5 block failure, but not in a 30 block failure. Sometimes shit just happens.
As for the HMO, well it's probably something people pay for so they usually can deal with the system being down. Free shit of course has to be up at any time because that's a God-Given *ENTITLEMENT* and we all know that the people in china/india/wherever will do anything possible to keep systems running 7*25*forever so you better do it too.
Ahem. These days, I'm pleased if anything works.
CZ