Open the pod bay door, HAL.

A tragedy of catastrophic proportions has transpired at my place of employment -- our server has crashed. Not just "fix it with control, alt, delete" crashed, but big time, "we're not sure when it will be up and running and if, when we do get it up and running, your files will still be on it" crashed. This is a Bad Thing, second only in badness to the time a few years ago when the server actually caught on fire (how the IT goons managed to pull that one off, I'll never know).

Meanwhile, progress around the office has come to a grinding halt. Without the server, we cannot send or receive e-mail, nor can we access any of the files that we formerly shared on the server. For a few days, we couldn't even access the Internet. So basically, we're all just sitting around, twiddling our thumbs and editing whatever manuscripts we'd already uploaded onto our computers before the Great Crash occurred, waiting for our ONE IT guy to fix the problem. He tried to explain what happened, but it just sounded like "blah, blah, can't boot, blah, blah, server, blah, blah, next week, blah, blah, blah, I make more money than you even though I work half as many hours...".

And because of my desire not to get dooced, I'm not even going to DISCUSS the unholy shitstorm that was the departmental meeting I attended earlier this week, nor shall I discuss the complaint I filed with HR against my boss (for an issue completely unrelated to the unholy shitstorm departmental meeting). Suffice it to say that it was bad... not as bad as a flaming server, but bad nonetheless.