Imagine this. A potential client is here for a demo. Of course, the stuff that is to be demoed, which was running perfectly last week, is no longer working because someone has been mucking with the webserver settings. Of course, I notice this while my boss is doing his sales pitch, because nobody bothered to check that everything was kosher *before* the client comes (and since I found out that the client was coming 30 minutes before he actually comes in the office, I can say that this should have been a big case of notmyproblemitis)
Frantically, I go in and start fixing stuff that's been broken without anybody bothering to tell me. I almost had to resort to troubleshooting rule #1, but I got everything up and running without the client ever noticing *buffs nails on shirt*
I rule, that is all.
Good job!
PS- I am usually downstairs in that back room.
(http://livejournal.com/users/saucylaur)
Thankyew, Thankyew veramuch.
Do you mean the room behind the bar, where the bands play, or the little side room with the lower ceilings?
(http://livejournal.com/users/talisker)
Lower ceilings.
I haven't been there enough lately. *sigh*
On a side note, what the hell is going on with this freezing rain today?
(http://livejournal.com/users/saucylaur)
Well, if you want a pub partner, give me a shout :) As for the weather, welcome to canada m'dear :P Were you here for the ice storm?
(http://livejournal.com/users/talisker)
just because I'm curious, what is the troubleshooting rule #1? Not my fault? Not my problem? Somethimg else?
frankly, there are very lucky to have you as an employee!
(http://livejournal.com/users/kaliko_mel)
For computers, troubleshooting rule #1 is kick it!
(http://livejournal.com/users/talisker)
Ha! NO. I JUST missed it – Thank God.
(http://livejournal.com/users/saucylaur)
you missed a hell of a party :) I didn't not sober up, from drink and smoke, for a solid week :D
(http://livejournal.com/users/talisker)