Back at GameSpy, crt had a habbit of making redical improvements just before taking off on a weekend ski trip.
And of course - everything would break and we could never reach him because of the *cough*bullshit*cough* excuse that he was in the mountains and out of cell range.
It got so bad that if anyone heard that he was taking off, they would quiz him about any changes. Eventially - he learned not to tell anybody before taking off. Sometimes the only way we knew he was leaving was when he would send an email just as he was going or from the person that gave him a lift to the airport.

GameSpy was not alone in this behaviour. For I present to you my current situation:

• Owner #1 - Coach: took off for Europe last week, he won't get back until the 22nd
• Owner #2 and lead programmer - Scott: (our crt) made a HUGE number of changes to the system last night and now everything is broken. BTW he took off for Florida on a red-eye flight last night and won't be back untill the 22nd as well.
• The only other Programmer - Forest: Just took off for comicon and won't be back until Monday.

That leaves me to reverse engineer all the changes that they made to systems that I've never touched nor known the existance of and create my own workarounds so that I can attempt to be productive today.

I'm living in a flashback, good times - good times.... :)