(no subject)

Today, we reprised, at least on a pain level, yesterday's Meeting of Pain.

Since development isn't likely to get a damned thing done today, testing certainly isn't going to happen. It's an unfortunate facet of my existance- there isn't testing for me to do until people write code and check it in.

So, since my day is being essentially wasted, i'm scraping the barrel to come up with Useful Things To Do While Trapped At Work™.

I've wanted a tool which will let me look at changes in the pre-compiled code base on an as-needed basis; because if i know what files have changed, i know what areas in which to expect to find potential bugs. This lets me be efficient by not wasting time doing test passes on things which have remained static. We don't really have such a tool at present.

I'm writing one. Command line is mah frien'. At this point, i have about 85% of the functionality i need. I'm still working on finding a handy way to use %date% and %time% in the path to distinguish one comparison from another, though.

(no subject)

Wheeee. Finshed my command-line file, and got everything i needed in it.

Off to DIE tonight with damashita and misskarin while the latter's eldest(?) child watches the boys.
Anyone else interested in joining us? L. from work isn't going to be able to make it again, and K. has had another schedule collision.