A Working Vacation
Two days ago I decided, at the spur of the moment, to take the rest of the week off. Where I work, we get the week between Christmas and New Years off. So taking the rest of the week off gives me a whopping two weeks off in a row! I have not had that kind if time off since I started working in the real world.
I am currently in day two of the vacation. How is my week of solitude to rest and recoup going? Not well.
Today, an issue came up that normally I would delegate to one of my underlings, but they are all on vacation in other countries. So, I needed to come to the rescue - as is my specialty. My accursed speciality.
So, at 8:30 a.m. this morning, the issue comes in and I get to work on it. Except that I cannot, because I locked out my account. Fun.
After a shower where I bitched and complained the whole time about having to work on my two weeks off, my account was unlocked and I started up again, more carefully this time.
I work the rest of the morning to reinforce my opinion, and convince everyone else my opinion is actually fact, that it is the responsibility of the person who reported the issue to fix. That's right, the people reporting the problem could have fixed the issue all on their own.
It boils down to this: Yesterday, everything worked fine. Last night, they did a big upgrade on their side an integration. This morning, their system has problems integrating with my part of the system - which did not change at all. So, naturally, they tell me I need to fix my side.
And, as it turns out, the issue is neither urgent or important. The integration between these two systems will not see any use until after my vacation is over. So, while it is a production system, and in IT we could not possibly say that this piece can lay broken for a few weeks until we are fully staffed and the integration will actually be used, but we could have swept this under the rug till January and gotten on with our lives.
Now, if you excuse me, The Legend of Zelda awaits.
I am currently in day two of the vacation. How is my week of solitude to rest and recoup going? Not well.
Today, an issue came up that normally I would delegate to one of my underlings, but they are all on vacation in other countries. So, I needed to come to the rescue - as is my specialty. My accursed speciality.
So, at 8:30 a.m. this morning, the issue comes in and I get to work on it. Except that I cannot, because I locked out my account. Fun.
After a shower where I bitched and complained the whole time about having to work on my two weeks off, my account was unlocked and I started up again, more carefully this time.
I work the rest of the morning to reinforce my opinion, and convince everyone else my opinion is actually fact, that it is the responsibility of the person who reported the issue to fix. That's right, the people reporting the problem could have fixed the issue all on their own.
It boils down to this: Yesterday, everything worked fine. Last night, they did a big upgrade on their side an integration. This morning, their system has problems integrating with my part of the system - which did not change at all. So, naturally, they tell me I need to fix my side.
And, as it turns out, the issue is neither urgent or important. The integration between these two systems will not see any use until after my vacation is over. So, while it is a production system, and in IT we could not possibly say that this piece can lay broken for a few weeks until we are fully staffed and the integration will actually be used, but we could have swept this under the rug till January and gotten on with our lives.
Now, if you excuse me, The Legend of Zelda awaits.
Comments
Post a Comment