GatewayRedbirds.com

"That's not a problem".

No [expletive] it's not a problem.

Conversation I just had on the phone:

"Hi this is Sally with Eegroblatz and I was wondering how you process your GIS information for tiddly wink blam blue sky?"

-- I have no idea what you just said.

"That's not a problem. Would you know who in your organization is responsible for maps?"

-- Maps? Like where am I kind of maps? Like how do I get home type of maps?

"Uh .... blubber blubber ... uh yeah, digital"

-- What are you talking about?

"That's not a problem. So you don't process diddly fud green grass blatz gif's?"

-- Uh ... no.

"That's not a problem. Thanks for your time.

...

Well you know what, it kind of is a problem [expletive]. Because I'm sick of these types of phone calls. The problem isn't that I don't know what you are talking about, it's that you asked the dumb ass question. I swear everytime someone says "That's not a problem" I just want to say "No [expletive] it's not problem".

I literally don't know what you're talking about.

I hate when store clerks say "no problem" after I say thank you. No [expletive] it's "no problem" because it's your [expletive] job you slacker. How about a proper "you're welcome" instead.

At the end of the day.

"It is what it is", really what else would it be.

When people are being interviewed, and they answer, "No, yeah I think that...". Or the reverse, "Yeah, no I will not."

Also, "job creators".

"That's fine," when I tell one of my guys I need something done. No [expletive] it's fine, I just told you to do it.

"Having said that..."

I hate people who say "impacted" when they mean "affected."