- if any organizers are competing, don't allow their teams to them enter
- don't let sponsors bother coders (a few brief interviews and a pitch at the beginning is OK, but asking everyone to do a survey is not the best idea.)
- explicitly have contestants outline what they actually built during the hackathon, or have judges go around and talk to people ala http://news.ycombinator.com/item?id=2240576. Or check git/svn logs.
- have contestants list # of team members so judges can weight this into their decision (otherwise winning is super hard for 1-person teams)
- discourage non-workers from attending and distracting coders
- if any organizers are competing, don't allow their teams to them enter
- don't let sponsors bother coders (a few brief interviews and a pitch at the beginning is OK, but asking everyone to do a survey is not the best idea.)
- explicitly have contestants outline what they actually built during the hackathon, or have judges go around and talk to people ala http://news.ycombinator.com/item?id=2240576. Or check git/svn logs.
- have contestants list # of team members so judges can weight this into their decision (otherwise winning is super hard for 1-person teams)
- discourage non-workers from attending and distracting coders