(no subject)

There is an infectious grumpiness sweeping through our company lately.  I don't know what's causing it, but it seems that every second bit of correspondence I've seen lately has come with a complimentary chip on the shoulder, just waiting for somebody to say the wrong thing.  I took a small dig at one of our programmers the other day to which he took understandable umbrage (a bit out of proportion to the comment, IMO, but it's not my job to tell somebody how offended they should be by one of my comments).  I apologized to him today when we spoke, and in turn he acknowledged that, in retrospect, my comments hadn't really been off-base.

I'm going to be extra cautious for the next while.  I don't plan to walk around on eggshells, but I am going to ensure that I behave in a professional manner and keep my personal feelings at arm's length.  I'm not sure that I have the solution to our current malaise, but at least I can avoid being part of the problem.

*yawn*

Libby: I got my authorization from GW.

This might even cause a blip on the media radar before the next runaway bride.

Nothing more to see here, folks.

Carry on about your business.

Beer tastes good

I managed to keep my new "professional" demeanour for almost an hour after posting this morning.  I made some changes to an application today and sent a link to the newly compiled executable to the project coordinator just after lunch.  About 45 seconds after I'd sent him the link, he called and said that the program was stopping and giving him a puzzling error message on the second screen.  As soon as he said that, I knew immediately what was wrong; I had forgotten to remove a hard terminate command from the program before re-compiling.  I'd put it there so that I could test out some field validation in the first screen.

I kept him engaged in conversation while I removed the break and recompiled the code.

Me: Can you read off the error code to me when it stops?
Him: Ya, hang on while I run it again.  (Sound of clicking, and then a critical stop sound.)  It says (reads off the error code).
Me: (Quickly moving the re-compiled code over to the production directory.)  Ah, well you're not clicking the "Execute" button hard enough.
Him: What do you mean?
Me: When you click the "Execute" button, press it harder.  It's pressure sensitive.
Him: (Sound of clicking) ...
Me: Did it work?
Him: Yes, it worked that time.  (A pause.  Slightly recriminating tone.)  plonq, we can't be putting out a program that's pressure sensitive.  We're going to have a hard enough time getting users to adapt to this program as it is.
Me: ...!

I'm so going to Hell.