Work Woes

Yo' - I never claim to be a technical resource. I've long since referred to myself as a "hacker" when it comes to any quick and dirty programming that I'm forced to code. When people at the office talk about "bouncing a server", I mentally envision a big burly guy throwing a waitress out of a bar. I ain't no tech geek.

However, when the person who's actually paid ($98K/year) to be a technical expert calls me late last night to discuss an issue with programming that hasn't changed since before I joined the company - offers no solutions - agrees that one very ugly solution (which I came up with) is our only option - then chooses to completely ignore that option after hanging up the phone (saying "but it would take hours to code") - and ultimately has no other solution 14 hours later.....yeah, I may be forced to call that highly-educated technical resource a MOTHER FUCKING MORON.

Listen, Fucker...3 hours of coding an ugly solution will always be quicker than 14 hours of no action. Don't you dare say I'll have to answer as to why the deadline is missed. I just may have to "bounce" you from the company.

Would it be wrong to suggest those 14 hours would have been better spent on Monster.com?