oh, yeah, i'm working on my "final" for my physio class now. it's kind of like a post mortem of the semester. for one of the presentations that I did, I'm supposed to say the things that were difficult about it and say how I solved those problems. The tomorrow morning we share and hopefully learn something from each other. Gotta really try to get to bed by 12 tonight so I can get up and get to school early (yawn) tomorrow.

Okay, so turns out I wasn't quite done with the program... geez. Well, there was one small bug that I didn't catch. Fortunately, my partner found it and I was able to fix it before demo'ing my project. Yes, you heard right, my partner sent me email. I wasn't sure what had happened with him - last I heard, he was out of town with a family emergency and was supposed to be back last friday. I sent him emails each time I finished fixing what I thought was the last bug, but didn't hear from him. Well, until today around 1pm. I was a little flustered at first, but everything turned out okay - at least I think it did. I ended up doing my demo anyways today cause we had some extra after class and even though there was a bug that caused my program to crash at the very end, the prof was pretty nice about it. I feel quite fortunate. Anyhoo, our original demo time is tomorrow at 4pm. I hope I can skip it and have my partner go himself since I have to be at school at 8am for my physio final, then off to work. So if I don't have to come back to school, that'd be ideal.

Bought tickets for the Matrix Reloaded today - going to see it on thursday. :)

Okay, okay. I THINK I'm done (well, pretty much) with my part of the program. I am worried though, cause I haven't heard from my partner all weekend. Actually, the ideal thing that could happen is if he decides he's going to take an incomplete in the class or something cause then we don't have to worry about integrating our two parts of the program. It's crazy. I feel like I've thought it's done at least 4 or 5 time already, only to realize that there are still bugs in it. I'm realizing the purpose of things like unit testing and the such that we do at work. Everyone hates it cause it's tedious, but I'm learning how necessary it is if you want to write a piece of code that doesn't break unexpectedly. Essentially each test that you prepare for your code can test a few or many logic paths in your code and all the tests that you perform on it can cumulatively test ALL logic paths. Then, when your program is being used, it'll be unlikely that a "special" file/sequence will break it. Boy, it seems like there have been so many times that I've seen that at work - and the time it takes to fix it just delays everything. Best to just get it done the first time. I guess i'm learning that.

Well, like I said, I THINK it's done now (minus that one bug which I can hopefully fix tomorrow). I'm afraid to test it with another file/testset cause it might not work again..... But I need to come up with a few more test sets and then get started/finish the writeup by tuesday. So I guess I should go to bed now so I can get up for work tomorrow.