Re: LTE 2.0
Posted: January 5th, 2014, 10:16 am
Sheree, so sorry about the passing of your kitty. Hugs and vibes and prayers for you in your loss.
-=OUR HOUSE=- A Forum for Fans of Duke Sports
https://crazietalk.net/ourhouse/
ArkieDukie wrote:Next installment of "As the Bunsen Burns":
As you may recall from my lengthy last installment, Road Runner asked me to lead things up on a project with an external collaborator, and Bar Minion caused trouble. She tried to make Brilliant Grad Student, another postdoc and myself look bad by sending Road Runner a list of things we had done wrong. Flash forward to today: I figured out that, unless I missed my guess, Bar Minion sabotaged our experiment. She tuned the instrument just before we performed our analysis, and she changed a setting to make the instrument perform in a less than optimal manner. I sent a nice little email to Road Runner saying, "I found the source of the problem. In our past experiments we used setting X; for this most recent experiment the setting was Y. I will check in the future to make sure this doesn't happen again." I did not directly say that Bar Minion did this on purpose because I cannot prove it, but the blame for the problem is now squarely where it belongs. Hopefully Road Runner can/will connect the dots.
On a similar note, today I had to help set up the instrument for the repeat analysis of the same samples. We decided to use a slightly different instrument method this time; it's one the Bar Minion used in the past to analyze another sample set. When we started to set up the instrument queue, after BM finished tuning it, we discovered that she had hidden the instrument method we needed (or just flat-out removed it from the instrument computer). The three of us spent an hour rebuilding everything from scratch. Oh, and we also had to fix the setting that she had messed up yet again. I sent another nice email to Road Runner with an update, saying we had to rebuild the analysis method because the other one was unavailable and that I had corrected the setting that was wrong yet again.
Seriously, if I was Bar Minion's boss, I think I would've fired her by now. If not, the most recent incidents would be the final straw. Unfortunately it cannot be proven that any of this was intentional - just the way she planned it. My gut tells me it was, though.
ArkieDukie wrote:Next installment of "As the Bunsen Burns":
As you may recall from my lengthy last installment, Road Runner asked me to lead things up on a project with an external collaborator, and Bar Minion caused trouble. She tried to make Brilliant Grad Student, another postdoc and myself look bad by sending Road Runner a list of things we had done wrong. Flash forward to today: I figured out that, unless I missed my guess, Bar Minion sabotaged our experiment. She tuned the instrument just before we performed our analysis, and she changed a setting to make the instrument perform in a less than optimal manner. I sent a nice little email to Road Runner saying, "I found the source of the problem. In our past experiments we used setting X; for this most recent experiment the setting was Y. I will check in the future to make sure this doesn't happen again." I did not directly say that Bar Minion did this on purpose because I cannot prove it, but the blame for the problem is now squarely where it belongs. Hopefully Road Runner can/will connect the dots.
On a similar note, today I had to help set up the instrument for the repeat analysis of the same samples. We decided to use a slightly different instrument method this time; it's one the Bar Minion used in the past to analyze another sample set. When we started to set up the instrument queue, after BM finished tuning it, we discovered that she had hidden the instrument method we needed (or just flat-out removed it from the instrument computer). The three of us spent an hour rebuilding everything from scratch. Oh, and we also had to fix the setting that she had messed up yet again. I sent another nice email to Road Runner with an update, saying we had to rebuild the analysis method because the other one was unavailable and that I had corrected the setting that was wrong yet again.
Seriously, if I was Bar Minion's boss, I think I would've fired her by now. If not, the most recent incidents would be the final straw. Unfortunately it cannot be proven that any of this was intentional - just the way she planned it. My gut tells me it was, though.
Yup, you understand.YmoBeThere wrote:BM = Bowel ??? Well, you get the idea?
OMG - I just got the pun here! VDB, I love you!Very Duke Blue wrote:ArkieDukie wrote:Next installment of "As the Bunsen Burns":
As you may recall from my lengthy last installment, Road Runner asked me to lead things up on a project with an external collaborator, and Bar Minion caused trouble. She tried to make Brilliant Grad Student, another postdoc and myself look bad by sending Road Runner a list of things we had done wrong. Flash forward to today: I figured out that, unless I missed my guess, Bar Minion sabotaged our experiment. She tuned the instrument just before we performed our analysis, and she changed a setting to make the instrument perform in a less than optimal manner. I sent a nice little email to Road Runner saying, "I found the source of the problem. In our past experiments we used setting X; for this most recent experiment the setting was Y. I will check in the future to make sure this doesn't happen again." I did not directly say that Bar Minion did this on purpose because I cannot prove it, but the blame for the problem is now squarely where it belongs. Hopefully Road Runner can/will connect the dots.
On a similar note, today I had to help set up the instrument for the repeat analysis of the same samples. We decided to use a slightly different instrument method this time; it's one the Bar Minion used in the past to analyze another sample set. When we started to set up the instrument queue, after BM finished tuning it, we discovered that she had hidden the instrument method we needed (or just flat-out removed it from the instrument computer). The three of us spent an hour rebuilding everything from scratch. Oh, and we also had to fix the setting that she had messed up yet again. I sent another nice email to Road Runner with an update, saying we had to rebuild the analysis method because the other one was unavailable and that I had corrected the setting that was wrong yet again.
Seriously, if I was Bar Minion's boss, I think I would've fired her by now. If not, the most recent incidents would be the final straw. Unfortunately it cannot be proven that any of this was intentional - just the way she planned it. My gut tells me it was, though.
Hang in AD. Surely BM can't get by dong this crap for ever.
Yep. That was intentional. It was a consideration when I chose the name for her.YmoBeThere wrote:BM = Bowel ??? Well, you get the idea?
My past strategy in dealing with this type of situation has always been to play stupid. If I don't tip my hand and let her know that I know, she'll keep up her antics at her current level. There's a greater chance that she'll eventually trip herself up with Road Runner that way. If I let her know that I know, she'll get more dangerous in that she'll change her strategy. She's already done that to some extent; she's gotten better at being more untraceable (for lack of a better word) in her actions. Anyone with a brain knows she's intentionally sabotaging her colleagues, but she's doing it in such a way that there's no solid proof. If I call her on it now, I become the a$$hole IMO. She would go crying to Road Runner immediately, and Road Runner would back her. Remember, she has a history of playing the "hostile workplace" card when she gets called on her BS. I'm hoping I can keep my current course and she'll eventually do something so blatantly insubordinate that Road Runner cannot ignore it any more.windsor wrote:You need to keep doing what you are doing. Factually reporting any issues that occur and hoping eventually the dots get close enough together for RR to see the logical conclusion. Sadly, it might take a while. Obioulsly, check all the settings before running any samples. Now, if I an think of a subtle way for you te let BM know you now....hmmmm