grammarwoman: (Default)
Dear B, you raving [insert your choice of pejorative name for a piece of female anatomy],

I have proven to you time and again that I am a skilled programmer. I also know that if I submit a piece of code to you that is anything less than flawless, you will show me approximately the same level of patience and courtesy as that of a starving, rabid Chihuahua with a porterhouse steak.

Please assume, then, that after a few very painful lessons, that I would not willingly give you code that has not been tested within an inch of its life. Please also check the date on the code in question to ascertain that you’ve had it for over two months, and then quickly glance at the error message on the compile log to learn the field name that was the cause of the failure. It may be the exertion of a few minutes to check the table definition, what with attempting to type with your festering claws, but I will optimistically give you the benefit of the doubt (that, incidentally, you have never shown me) that it would not have taken you very long to realize that the field name was changed by someone else between my release of the code to you and today.

I would appreciate that, in the future, you would not automatically assume that such errors are my fault and drop the task on my desk with the sort of sneering condescension that you just displayed to me. I realize the futility of my request, as I have demonstrated my competence to you in similar situations countless times.

In short: fuck you, you oozing hosebeast.

Kisses!

[livejournal.com profile] grammarwoman
grammarwoman: (Default)
I may have mentioned once or twice that I don't like my job. However, upon further reflection, I realize that what really drives me to despair is my coworkers.

Exhibit A: The project I'm working on has been a nightmare from day one. It's been four years since the last update, due to various department politics and feuds. The guy who wrote and maintained it was pre-emptively pulled off it, so another guy with little Visual Basic experience could do the bulk of the programming. (Brilliant!) As a result, the program has been buggy and unreliable, and the rest of the team has had to pull long hours and work weekends in testing and fixing. I'm all for teamwork, but I resent like hell having to put in extra effort to fix someone else's mistakes (especially because if I were submitting such crappy code, I'd have had my ass chewed off). I've started referring to this as sweeping up after other people's elephants.

Exhibit B: I hate the word "perception". It is the perception among my (busybody, fishing-for-faults) coworkers that I do nothing but surf all day. (Never mind that the majority of them are checking their stocks, email, sports scores, and weather reports whenever I walk by.)

Evidently now, it might now be the fucking perception that I'm involved with my coworker Chad, because I sit with him at lunch and we went to the convention a few weeks back with our friend Candi. (One guy sniped that "of course you guys have to sit together at lunch - you always do!", and another commented that it was convenient that Chad and I both had errands to run today at lunch. I would have laughed off the first, but the second put my hackles up.) It has nothing to do with the fact that we're both geeks who watch the same TV shows and most of the rest of people we work with are conservative, sports-watching, gossiping Republican assholes.

I desperately need to get out of there.
Page generated Apr. 23rd, 2025 06:09 pm
Powered by Dreamwidth Studios