The latest thing that is driving me crazy: The word "should." We're having trouble with a tool at work, and the tech guys are trying to fix it. Here's how our conversations are going:

Me: Hey, Wilson, the CMS won't let me use the Assign Documents function for the Canada site.
Wilson: Hmm. It should be working.
Me: (beginning to froth at the mouth): I know it should be working! That's why I'm talking to you! Because it isn't!
Wilson: Well, did you try this?
Me: Yes.
Wilson: Hmmm. That should work.
Me: (sparks flying out of my ears) Yes. I know. It doesn't.
Wilson: Yipe. (Ducks under desk)
Me: Sorry. I'm calm. (Deep cleansing breaths) I know exactly what it should do. It should work. It should be an effective tool. It should make my job easier, or at least not 10 times more difficult. It shouldn't make me want to fling myself, my computer, or, for that matter, my tech department out the window from a great height. But is doesn't work and it is making my murderous.
Wilson: (peeking out from under the desk) I'll get back to you, ok?

I went to doublecheck something with Andy -- I wanted to make sure it wasn't just me who was having this problem -- and he said the same damn thing. "Wow. That should work." Arghhhhhhh. He escaped with his life, but just barely.

I don't want to get angry at Wilson -- he's a great guy, he's been dropped into the project, he's doing the best he can, and it's not like he's incompetent. It's just that this is at the bottom of tech's priority list -- and I understand why -- and we can't get it fixed. But that means we can't actually do our jobs in an efficient manner -- or at all, in some cases. Which pisses me off. If my actions are useless here, I might as well not even bother coming into work. I'd be much happier sleeping in, reading, watching Buffy, hanging with the cats..... if it weren't for that pesky mortgage/food/clothing thing. Sigh.