Massless

I was writing a Java app for Linux a few days ago. I don't usually have that opportunity in my Windows-centric place of employment so it was a nice change of pace and a chance to work on a seriously stable system. But...the app kept crashing with some mysterious message called a "segmentation fault." So I decided to look for some info about it...

You, on that Mandrake box over there. Why are you giggling?

Shit. I had no idea that the segmentation fault is (at least from my perspective) the Blue Screen of Death for Linux. It sucks to spend hours troubleshooting the OS when I need to be writing code, but I have to accept that no matter the OS, I will be encountering mysterious-seeming and frustrating roadblocks when attempting to get work accomplished.

To keep things even, I must tell you that I've somehow mysteriously caused enough IRQ errors in an instance of Windows 2000 to have initiated three BSODs in a single week. A-ah-arrrgh.

What a mood I'm incubating. At work I am in super-bug-fixing mode due to an upcoming software release so I'm surrounded by failings and missteps. (Others' missteps, naturally, since my work is perfect every time and never needs to fixed or reviewed or second-guessed...wait, where are you going? :) Also in the spirit of broken things, I keep hearing the mistakes (and blindly disregarding the virtues) of TV Highway to the Stars, our album. Broken app, broken operating system, broken song, broken software. But on the other hand (...)

My Dad typed something during a test of BlogLess. It was this:

iT DOESN'T MATTER WHAT WE DO HERE, i'M juST PRACticing.

Hm, I'll buy that. Check it out. All of this...everything here...

I'm just practicing.