Madness the day before going on PTO

It was a crazy day for me today. First, it is the last day at work before going on a 2 week PTO, or Personal Time Off. It’s a fancy word for vacation. I was amazed at how many people didn’t know that acronym. I thought everyone knew that, but I guess that’s what’s popular in the faceless, cold corporate world.

Over the weekend, we had a problem with one of our services that we provide to customers. Without going into any detail, the problem was related to DNS resolution. In fact, I got a voicemail on Saturday (I couldn’t hear my phone ring because I was on the way back from Marshall Wall). I guess sometimes being the go to guy can suck, can’t it? Anyways, I got a call from one of our developers this morning, and they were wondering how did the incident over the weekend get resolved. Well, it just got resolved, but we didn’t know what happened … we didn’t get a root cause analysis.
Now part of the assinine IT policy is that any ticket filed that is a P1 needs to be validated by a manager. So even if the world is crumbling, customers are down for 6 hours (as was the case today), the ticket will still be left as a P3. The developer, who opened the ticket, didn’t know about this rule, so this issue was left collecting dust, to be handled as a P3. Afternoon came, and there was still no movement. I decided to call the helpdesk, with ticket number at hand, and damn it … I needed manager approval for P1. So instead, I just called the guy who was handling it, and finally got some movement on it. Just checked, and DNS is now working, and the issue at hand is now resolved.
In addition, it is April Fool’s Eve, or the eve that the conficker.c worm will launch. As you can imagine, this saw a lot of activity with knowledge base, security response teams, and many customer calls inquiring about this. What was frustrating was explaining to some people how anti-viruses and intrusion detection and prevention systems are different. Had to explain how the architecture is different, and there is no way the general customer would understand that. But I had to go through that laborious exercise … oh well. Just another security red alert type of exercise.
Then, I had all my cases that I had to transition to other Engineers. So that was a big time dump, explaining what the status was with my boss, even though I had it all documented in a nicely crafted email. I should have just bypassed the whole email process, and just explained it to him in a room. But then again, he would want it in email … doh!
Oh, and then I had to post two software releases today. As luck would have it, the web team had some meta-data issues with the server. Whaddaya know … posting the release is not gonna happen today. Now, I had to scramble and let all my backups now what is going on, and the day where I was supposed to get off at 3 PM, I was still working on stuff till 6:30 PM.
It always seems to happen this way … the day before going on PTO, is the busiest. If anything could go wrong, it will go wrong. Well, at least I didn’t lock myself out of my house (which I did one morning … that was more embarrassing than anything else, especially since it was 6 am, before most people are awake).
Ok, now time to figure out what the heck I am going to do for the next couple of weeks. One week will definitely be in LA, visiting dad. Maybe hook up with ME for a few rides, and maybe hook up with some LAUSD teachers, who have spring break off that week. Only drawback is my friend Mary (no, not ME, my other friend Mary), doesn’t have the week off till the week I go back. Oh well. C’est la vie!
This entry was posted in career, work-related. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s