MAMEWorld Forums - The Loony Bin - I shait you not....

I just recieved an "Attaboy" for fixing the rejection issue...

Wow.

> A project manager walks up to me two weeks ago and asks status on product xxx.
>
> I state that simulations are showing a trend toward rejection issues, but there
> hasn't been any sign of that in live data. I say I will be working on verification of
> the simulation code.
>
> Today a VP of engineering comes up to me and says, "Hey, what can we do about the
> high rejection rate on product xxx"
>
> "Haven't heard of any issues so far, I'll go check it out to be sure"
>
> I go talk to the technicians, they know nothing about any issues. Product xxx seems
> to be OK.
>
> President of engineering comes up to me and says, "VP says we are having rejection
> issues on product xxx, what is the issue?"
>
> "Checked it out, didn't see an issue sir. I'll look again just in case I missed
> something"
>
> 2 hours go by....
>
> Boss comes up to me and says, "Hey, I just got out of a meeting with the VP and P,
> they were talking about rejection issues on xxx..."
>
> I explain to my boss that there isn't an issue, never was an issue, not sure why they
> think there is an issue.
>
> Boss wants to go with me and check a third time. We do so. We run the hell out of
> product xxx. No issues seen. Data to back it up.
>
> 2 hours later, I get a meeting notice. "Action plan on product xxx"...Christ.
>
> The meeting begins with "italie, can you walk us through the issues on product xxx"
>
> I explain there isn't an issue.
>
> They want to know what changed because certifications are involved, I can't just
> change things without committee. I explain that nothing has changed.
>
> They want to know how I fixed the issue without changing anything.
>
> I explain there was nothing to fix.
>
> They want data to back that up. I supply data that product xxx is running OK.
>
> They want to know why it's OK now.
>
> Again I explain there was never an issue, far as I can see.
>
> They want to know who claimed there was an issue.
>
> I explain the first I heard of it was from the VP.
>
> VP says he heard it from the project manager, when I told him I was working on
> rejection issues. (~great...I see where this is going~)
>
> The "consensus" is that since we don't know where this started (read: project manager
> threw me under the bus because he can't understand words), we must write up an action
> plan to monitor product xxx for a week. Just in case.
>
> FIVE HOURS LATER, the meeting ends. Three of those hours are "overtime" (sucks to be
> salaried sometimes). For a problem that never existed.
>
>
> Thankfully I have some bourbon left in the bottle. Going to need it.