Quote Originally Posted by baja_yu View Post
In that case I suggeste a controlled type, in your school classrooms. These are some points I would consider.

1. How many problems/tasks will there be? 1 to 3 is a good number.
2. What programming language? Take into consideration only those that are taught on your and other colleges. Consider using more than one. For example C++ and Java, separate or similar problems two solve, winner for each category.
3. Time available. Up to 3-4 hours. Anything more will be hard to endure.
4. Single entrants or teams? Can people work in teams or will each student work on his own.
5. Don't announce the problem ahead of time. Only give them the language and a general area.
6. Number of contestants. This depends on how much space (how many computers) you will have available.
And also how will you be judging the entries. What are the criteria to decide on which code is the best of the lot? Would you go by technical specs such as performance and memory management, or by functional specs such as how much of the problem has been addressed in the code, or by both? If both, which one gets priority, for e.g. one code provides a complete solution but has poor memory management while another code is unable to completely address the problem but has some excellent memory management, which one wins?

It would help if you came up with a clear and concise policy of deciding the winners and published this policy just before announcing the problem, at the start of the contest. This will help the contestants focus on what's more important. Take into account all the possible complications you will face when the decisions have to be announced. If possible, involve some senior (HoD) from your college in the criteria selection.

.