Jul 25, 2007 11:49
So, picture a report that you do every day, several times over (for several different accounts, say), and it must be updated several times a day to give you a snapshot of what the day looked like at 10am, noon, 2pm, etc. While picturing this report, make sure to imagine it as complicated a report as you can, each one taking a fair amount of time to complete.
Now imagine that you're having system "issues"*, and it's affecting your data integrity. So, now, not only do you have to update your report, but you also have to fix yesterday's reports, using antiquated back-up files that are only partially complete and might not even then be accurate. Keep in mind that you'll have to do this tomorrow for today's reports too, since these system "issues" are continuing and are still affecting your data.
Oh, and the "issues" randomly wipe out whatever it was you're working on so you have to start over**. It's been a GREAT day so far!!
* IT-speak for "it's screwed."
** Our supervisor asked us to email her whenever we lost connectivity (and thus data). I kept a running tab in an open email message and sent it at 8am (after I'd been there for a few hours). When she came in and read her email, she immediately stormed back onto the floor and said, "Have you seriously lost connectivity ten times this morning?!" (A usual number for this type of problem would be once or twice in a whole shift.)
And our heat wave continues. It's supposed to thunderstorm tonight, but then it's supposed to cool off a bit. I'll believe that when I see it (heavy rains seem to just add to the humidity rather than cool things off), but - man, how I hope it's true.
work,
frustrating