Don't expect people to commit up front to representing LessWrong. The idea of representing the entire community sounds kind of intimidating. In general don't stress benefits like getting positive publicity or learning important things about cooperation too much. I think that people who'll participate in a competition like that will be those who find it intrinsically rewarding. So stress the fun and coolness factor, I guess? Maybe have the people who participate initially write down the accounts of their early experiences in order to capture the imagination and draw in others.

It would be good if people could try their hand at participating in a team without too much commitment. This sounds hard and probably heavily depends on the structure of the particular programming problem and maybe rules of the competition.

Have a ready-to-use platform for cooperation so that people can immediately jump into team activities. Preparing such could amount to researching various websites providing such services, choosing the best combination of them and then writing a short tutorial on their use. In the extreme case, a group of volunteers could give the chosen solution a test run by cooperating on solving a problem from some prior programming contest and then writing down a report of their experience.

As promised, a few more postmortem thoughts.

I made a number of mistakes while writing my bot. (I'm about to compare my approach with that of the winner, xathis, so you might want to read his write up first: http://www.xathis.com/posts/ai-challenge-2011-ants.html)

I assumed I wouldn't have time to do the number of local searches that xathis did, and I never tested this assumption.

For the combat code, I wrote both minimax and probabalistic algorithms; both worked ok, but I never tried to do any branch pruning, so the minimax code only ran when small numbers of ants were fighting. I should have tried some branch pruning. I spent too much time writing the combat code for the benefit it gave my bot.

My biggest mistake, or perhaps the unifying theme of my mistakes, is that I spent way too much time searching for the Deep Underlying Principle; instead of just writing code that directly did what I wanted, I was trying to write code that produced the behavior I wanted automatically as emergent behavior.

I spent too much time trying to fine-tune doomed approaches (of course, that is at least partly hindsight bias). I should have spent more time exploring completely different approaches.

One thing I did do well was an algorithm for listing all local combats, so that my fighting code could run on small(er) numbers of ants. (xathis did something similar.) I'm also not unhappy with my BFS algorithms; they ran quickly and I should have thought to use them more heavily.

As far as working with an "official" less wrong team, I didn't feel sufficiently confident in my abilities to want to represent LW officially (and I'm not updating that belief much because I still think it's quite likely that lots of people here could have done better). I think if there is interest for next time, we should at least figure out a method of working together beforehand.

I'm not sure what else I should say, ask questions if you have them.

There are a lot of standard software development processes that you can follow. (e.g. SCRUM)

What those usually boil down to is:

• Now exactly what tasks need to be done.
• Now exactly who does what task and when it will be completed.
• Check both assumptions regularly.