Development is really cooking over on my new project. We have not one, not two, but three coders working on things. My major project today was cleaning up the items script. Considering that I cut the damn thing down from ~500 to ~250 lines, I’d say I did a fairly good job at it.

The only complaint I have is the current server’s (which we won’t be staying on for much longer, I believe that we’re getting the hell away from that host as soon as we get to beta) PHP config. Display_errors is set to off, meaning when a script has a parse error, it dies and doesn’t tell me why. That is probably the most annoying thing on earth.

I mean, how much would you like to have just gone through 250 lines of code, uploaded, and had it not work? Where do you begin to search for an error?

The solution was to comment out large portions of code to figure out the general area of the error (because the page won’t just be blank if doesn’t give an error), then zero in.

Yea. It’s going good. But moving on to the next matter of business…

I haven’t been taking many photos in the last few days. I guess the novelty of having a digital camera has worn off. So I was thinking about projects I could do with the camera, and all I came up with was a ‘day in the life’ sort of thing.

Kinda like a photoblog for a day. I’ll carry the camera around, fill a few flash cards with high-res images, bring it all home, and then dump it all on kato and do a writeup to go with it.

I figure it would probably be best to do this on Tuesday, since that’s an A day, and my A day teachers are generally more cooperative and friendly than the B day ones.

Mm. Yea, that’s all for today.