This was so NOT in my job description.

It came to my attention today that I have not posted in an entire week. WTF? I mean, I can see missing a day or two, but an entire week? In my defense, I did have to run to the Main Office, which not only adds an hour to my commute, but they tend to be a little more strict on work web access there than in my remote office here. Meh, what do you do?

To the best of my experience, with any given job, there is a certain level of "bend over and take it"-ness, and that it really is impractical and unwarranted for me to complain at all about what I am going to be forced to label as one of the better jobs that I have ever had. And I suppose that people are continuing to use VB6 much for the same reason that there are companies out there that are continuing to manage COBOL systems. They're in place, and they work. Kind of.

So the other day I was voicing an opinion of VB6, when a co-worker of mine, Speed Racer, gave me one of those quizzical looks that imply "what're you talking about man? You on drugs again?" "VB's not so bad" he says, "It's only a marginal pain in the butt, I was a Java developer before I came here, and sure there's some differences, but it's not that bad!" To which I replay "As a Java programmer, you don't have a soul to crush, so it doesn't surprise me VB doesn't hurt you."

I bet you can now guess what my next project is in. Damn.

~M.