ICFP Programming Contest 2013 – pre-registration required
research.microsoft.com
research.microsoft.com
this was the first "competitive" programming i had done (i've been a software engineer for years, but never entered competitions). i was wondering if the above is normal for a first time, and whether it gets easier (and more fun) as you get more experience. anyone got any advice? thanks.
Pacing is always a challenge. My own takeaway from the last few ICFP contests has been that ICFP encourages careful pacing by the gradual delivery of changes to the problem. If you put all your work in at the beginning, you might win the lightning round, but there's a good chance you won't have the energy to cope with the final twists. Or so I believe anyway. We'll have to see how this one goes.
Teams that do solve much of the task problem, or fare well against the bots (for competitive tasks), tend to be either researchers or graduate students studying the same field as the task's core problem, or teams of 5-15 people, or both!
Sometimes (on the more puzzle-oriented tasks like CBV or Save Endo) have hidden tricks which you might just not notice. (To their credit, those tasks had a lot of breadth, so there was plenty to do even if you missed the tricks, and if you didn't care that the trick was worth an outsize amount of points (like the Windmill in Save Endo).
I have a bad habit of using ICFP as an opportunity to learn a new language, and then waste a lot of time just learning the basics and system configuration. To make progress on the task, you need to work in a language that you already know like a part of your body.
You can easily spend several weekends playing with a task post-contest.