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.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
Not as critical as my boss thinks
Date: 2009-03-02 03:51 pm (UTC)I tried to imagine an emergency that would require me to fix a JDE report in the middle of the night or an IT problem that couldn't be better solved by any one of the twenty other people in our department. But hey, if I'm the only one left, we have a more serious problem that a phone call is not going to remedy.
But free cell phone, yay!
At a conference, a vendor was telling me all about the joys of RFID tags for warehouse inventory. I told him our assets were commercial retail spaces that tended to stay where you put them. And if they start moving or you can't find them, there are usually hurricanes involved, or Godzilla.