so i'm still working on my thesis. as it stands, i seriously doubt i'll be able to finish the first draft by the end of next week. on the bright side though, i did some profiling of my 20k+ lines of code, and cut the execution time by roughly five times. one really bad design choice accounted for the greater part of that... a run that previously took between 11 and 14 hours, depending on the load of the machine, now takes little over 2 hours.

i feel the need. the need. for. speed.

edit. i stand corrected. it's a very good feeling. when running a more extensive test, i found that what my software previously required 12 days to do, it now does in 12 hours. and i couldn't have done the profiling any earlier, since all the functionality wasn't in there until recently. what i've learned in the process? don't guess as to where cpu time is spent, use a profiler to get the facts!