this page intentionally left blank

folks, this is what happens when you decide “if it ain’t broke, don’t fix it” in regards to keeping your damn software up-to-date.  when it does finally break, nearly a decade and a half later, no one can fix it.  why?  because you have a vendor app that was written with Borland C++ 4.5, and i can’t get my hands on that to create a debug version of the exe, that’s why.  and XP doesn’t want to let a 16-bit windows debugger run (there is probably a workaround for that, but dear fucking god!  you’re still using a 16-bit system!). 

honestly, we even keep the damn cobol on the back end at the current version, and that language used to use punch cards.  not to mention that it pre-dates, well, me.  but no.  i’m stuck supporting your shitty little system and learning all about obsolete versions of languages, since you never saw fit to upgrade from FoxPro 2.6a and your app apparently uses Clipper to read dBase III tables.  it’s not even comprable to learning latin; i’m learning etruscian instead.

i’d smack whomever is responsible for this system never being upgraded or having the business moved to a different system.  but i don’t know who they are and i suspect they are in iowa.

This entry was posted on Thursday, November 20th, 2008 at 1:23 pm and is filed under ideas that in retrospect were not such good ones, lunatics, assholes, work, idiocy, rants, irritation, geeky, babblings. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.