Why bother with analysis of your opponent's approach. I think the real way to tackle this would be to already know your opponent's tactics. You can do this by submitting heaps of "different" entries to the competition (not sure if this is valid as the site seems to be/.'d), and since you then have a good chance of coming up against a program you have written, you could easily beat it!
That's sure to get you through a few rounds at least:)
I remember an incident during my final year of CS when the power to the entire building went down. (I said "remember", not "fondly remember")
The realisation that everything was a lot quieter, when we hadn't really noticed the noise before was quickly replaced by the noise of hundreds of screaming students and sysadmins.
Now I find the humming of a fan quaintly reassuring.
Slashdot Mirror
Juno pops up ads
NetZero wants to sue them
Free ISPs suck
You can find the website for MovieAction (the Unicef/Neeson project) here.
I dread to think of the assumptions that have been made in electrical and electronic equipment that would be affected by this!
Quake movies are made
Slashdot - "technology leap!"
Quake haiku is next
Radioactive
eBay auctioneers make a
Nuclear web site
Slashdot questions RAM
But no links in this story
Sites stay up today
Drunk Linux users
.cx domains
Will forget to register
Cities make weather
Slashdot readers make chatter
Redmond makes blue screens
Penguins in trouble
Slashdot readers quick response
Kills the webserver
That's sure to get you through a few rounds at least :)
The realisation that everything was a lot quieter, when we hadn't really noticed the noise before was quickly replaced by the noise of hundreds of screaming students and sysadmins.
Now I find the humming of a fan quaintly reassuring.