not so happy about wednesday

all was good until i got to base this morning. the kid was guarding, and i got a phone call alerting me to the fact that a montrous section of our systems is experiencing technical difficulties.

it's a side of our system that hasn't been touched in years, and nobody - not even our beloved previous TL - has any clue how it works. or why it does what it does. i don't remember ever scanning code so repulsive and confusing. and i can't understand a damn thing from the comments (we won't talk about my hebrew incompetence).

and because it's almost the end of the week - a fact which i'd been celebrating cerebrally - we're under intense pressure; if they'd informed us two months ago, when the problems began, we'd have been better prepared. now we're supposed to finish fixing it in less time than is realistic for learning what it is and where it comes from.

my headache is unreal, my team upset about the screams of anguish. so tomorrow morning i'm off to the induction base, bright and early, to go and pick up material that should explain what's supposed to happen. oh, and my ear's still smarting from the shouting i had to put up with over the phone.

as i said to the kid this morning, before i got that call: we desperately need to improve the documentation, and quickly. it makes too many assumptions, and even if we manage to deal with it, our replacements are going to be totally screwed otherwise.

and *i* got shouted out when i came into work. the lead made a mistake on the server, and the load is unmanageable. and he's off on holiday.

and spot. BAD DOG, spot. BAD DOG. didn't we learn not to test things in production? the dealers are all upset because the new settings don't allow them to do their jobs. and i'm taking the heat because he's not in.

today sucks.