On the (Imagine Cup) road again
This monday - finally - I found the time to check back to thespoke and look at the just opened IC categories Algorithm and IT. Last year I only did Visual Gaming, so this year I wanted to see what else goes on - before turning back to my VG solution and start adapting it to this years SDK.
IT is clearly not my area of choice, never really looked at Win2003 and Active Directory, looks like it's not really part of every day developer life.
Algorithm on the other hand sounded really exciting. The one thing I'm really disappointed about is the fact that the algorithms you need to build for Herbert are extremely specific to Herbert and have nothing to do with the 'real world' of algorithm development. First of all, algorithms in 'h' are judged by code size - seriously, in today's computer world, who cares how big a core algorithm is compared to the massive load of multimedia data? Second, they encourage to send Herbert on very long, detouring (and for the most part indefinite) tours around the map - so even if the program looks really smart, the path Herbert will follow definitely won't.
So after going to the International Olympiade in Informatics in 2001 and 2002 I know there are much better ways of testing people's algorithm skills than to let them send robots through an artificial maze.
So after getting side-tracked by those invitationals a bit I finally returned to my first (and so far only) love in the Imagine Cup, Visual Gaming. The contest itself still runs with the same slow motion as last year (Richard promised a final SDK (for the .Net RTM) on the 1st of December and we are still left with the Beta-2-SDK), but if there is one thing we learned last year it's that complaining about this sort of thing doesn't help. So I won't list all the holes in the SDK and instead say that I started adopting my solution from last year to .Net 2.0 (RTM ;)), and got the path planner up and running with the blood streams. With some new plans to deal with the NanoNeuros when I get home from Dubai it should produce at least the same quality as it did last year. (And then I'll have plenty of time to do all the tweaking that was cut short the deadline last time).