I got to work this morning and immediately began working on the Big Important Issue That's Eating My Brain. I took a break from it in the mid-morning to attend a meeting regarding the trip I'm scheduled for to Dallas next week. *waves to Dallas LJ folks* When I got back to my office, I started looking at the program I wrote to help search out bad data and destroy it when I noticed something...odd.
That sinking feeling in the pit of your stomach? Yeah, go with that.
You see, at the beginning of the week, we divvied up who was going to be writing which utilities. Each division got assigned the ones that they are the experts in. Simple, no? Yesterday afternoon I flipped out and demanded that another team send me their finished product because, hello, the deadline was yesterday noon.
I took a look at what they sent me. I tested it. Then I started cursing. The search that they had found worked. It'd been tested and released and is available to all who use our software. But, it searches exactly the opposite of what I needed. I need to find bad data - the search they gave me will take bad data and tell you where all it is in the system.
This? Not so much useful.
So I started writing my own code. I took what I'd already done, what I knew of that application, and a couple of handy tools and I wrote the capability into my search to pull off the one that the other team utterly dropped the ball on. As I was recovering that fumble and heading to the endzone, my phone rings. I glance to the caller ID. The COO (Chief Operations Officer, 2nd in command of the company) is calling me.
We talked for 15-20 minutes about the Big Important Issue That's Affecting More Than Just My Customer and what I and the other people working on it were doing to fix it. He wanted some background as to why it happened in the first place, how we identified the extent of the problem, who was working on it, who all would be affected by it, and what plans we have in place to help out the other customer teams who will need to deal with it.
After he hung up, I called the rest of my team who were all like "WTF, mate?" I also called my team lead and said, "I need some help here. These other guys won't answer the phone or return my calls and I need this done in 90 minutes. I'm also on the verge of a nervous breakdown, so any help would be appreciated."
I also had Downwood call to remind me that I have a life outside of work, and it's a pretty darn good life.
The code got done. I got to sit in a meeting with Big Important People and say, "Yes, I think that we've done what we can. If something else goes wrong, so be it, but we've covered all the places we foresee problems happening. I'm willing to do the work, but I need help validating it and making sure it's all good."
Because of this mess, I'm not going to Texas next week after all. They said that they don't want me to hand this off to someone else to finish and that making sure that this goes well is more important than the other trip. I think that they're right in that no one else at the Evil Empire knows as much about all the parts of this Issue as me, though I was looking forward to escaping the drama and pressure for a few days.
Leaving work was a trial in itself: I found myself locked out of the house and the coffeeshop where I was going to wait for Downwood was closed. Luckily, my ride didn't just abandon me, so I got a glass of wine and Dune until he showed up. Then, I got a burger, a really good beer, some yummy fries, and the final book in a Series of Unfortunate Events. I'm going to go pass out now in preparation for a makeover and Day Out With The Girls tomorrow.