I found this after doing a search for something I found on my good friend Poopie's site. By the way, tomorrow is her birthday, so get on over there and wish her a happy one. If you're a good lookin' guy, you might want to add a smooch or two.

I could write a post about 300 pages long about the events of today, but I'll try to give you the Reader's Digest low-down.

I woke up this morning, ready to tackle the issue with my project. I ended up with analysis paralysis and had to move to a different project, hoping that somehow, magically, my subconscious would come up with something.

I decided that my subconscious was probably on a milk carton somewhere, because it sure wasn't anywhere in my vicinity. I couldn't think of anything to make the situation any better, and finally resigned myself to give up on plan A. That left me with no choice but to work with the antiquated software that I've come to despise, and the knowledge that I will have the same user registration problems that I had last year.

Trust me. It was a mess.

It also meant that a gazillion of the (free) overtime hours that I put in, were all in vain.

But it also means that the gazillion overtime hours I had ahead of me were basically not necessary anymore. Sure, the design and functionality won't be as cool, but the majority of the work is done. Still, that left me with the registration issues.

Today was the last day for my reviewers to give me comments on the final review. One of those reviewers, who manages a training design team for another division, wrote me a note telling me how great my training looked (well, yeah, of course it does.. hee hee) and then asked me how I planned to roll it out. I briefly told him what I was up against and how disappointed I was with what I'd ultimately have to do.

He wrote back that he knows exactly what to do and to give him a call next week and he'll walk me through it. Problem.Solved.

This came on the heels of a meeting I had with another training manager who was intrigued with the database I built using MS SharePoint to contain my training content. During our meeting (which included her team), one of them said, "we don't have the skills in our department to do what you do." There was also a mention of me being SharePoint 'queen', but I sure wouldn't want to brag. *snort*

Oh, have I mentioned that someone from London called me to help them with SharePoint? No? Well, that proves that I'm queen.

Anyway, this department is able do things I have to rely on another department (that works at a snails pace) to do for me because I don't have the security permissions. Sooooooooo, I made a deal with them, that I'd create their database for them if they'd do the things I can't do- and put a rush on it. They think they got the better end of the bargain. Perhaps it's the way I spinned the idea?

They don't call me Spin Sista' for nothing.

Two disasters averted.

Disaster number three? Well, based on an email I received today, it looks like it's very possible that it may be impossible to complete through no fault of my own (isn't that ALWAYS the best way?) It's one that I've been dreading and only working on when I feel brain dead from my other current projects. The worst part was/is yet to come.

Who knows, maybe I'm interpreting that email incorrectly because clarification that I've asked for hasn't been given to me yet.

All I know is that I'm closing shop for the weekend starting oh, about 1/2 hour ago when I started this post.

The bearded eye-roller and I are heading out to the Willamette Valley to sample this year's Pinot Noir offerings. We'll be the ones in the red corvette with our top off.

Shame on you! I meant the top of the car. Sheesh.