Huh!

Well, worked a little, lived a little, died a little.
My code for the IEOR 162 project seems to be functioning fine after 2 hrs of work. This is amazing because writing crap from scratch in a semi-unknown language usually takes an incredible amount of time. I suspect its buggy but don't want to waste too much time checking the solution by hand. Will just occassionally glance at it and if inspiration hits me, that would be very good. ;P

The "vexing" problem in the research code? Well, tech support apparently mailed us a fix 3 hours before I found out what was wrong. Highly annoying, but I guess you can't learn unless you make mistakes. F was right in the sense that "these folks know their own code forward and backward and can probably pop the solution out in 5 seconds." I guess its just that I'm not usually willing to a) let a problem sit and b) bother other people with something I think I can fix myself... I guess I don't exactly have that sense of trust because 1)I'm a student and I do everything on my own and 2)the last times I had cause to rely on others they returned results which I wasn't too happy with (army and JC).

Made a midnight, on the spot change to my schedule for next semester again. If the system was managed by a real person s/he'd be smacking me for being so indecisive. Now the question is how to squeeze myself into the class I'm waitlisted for... I could ask for a leg up by a Profs I know, but that's both cheating (which I don't think I mind so much) and difficult (because at least one Prof has strongly advised against doing the very class I want to get into)

Looks like I'm off the hook for at least one assignment this weekend, so I can concentrate on the others. Huzzah! Have dinner planned for tonight, so I guess things are good. So now back to work...