These rules are based on the standard competition rules used at MLH Member Hackathons.
The spirit of the competition
Remember that hackathons are like marathons. Some people go to compete but most people take part to better themselves and have fun. Whatever the reason is you’re at a hackathon, make sure you’re upholding the hacker spirit by collaborating with other teams, helping beginners, and having fun.
The rules of the competition
- The maximum number of hackers per team is limited to 4.
- Teams should be made up exclusively of students (or recent graduates within one year of having graduated) who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
- All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine.
- Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
- All work on a project should be done at the hackathon.
- Teams can use an idea they had before the event.
- Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.
- Teams can work on an idea that they have worked on before (as long as they do not re-use code).
- Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
- Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.
- Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it’s okay to fix that. Making large changes or adding new features is not allowed.
- Projects that violate the MLH’s Code of Conduct or HackCU’s Code of Conduct are not allowed.
- Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking MLH’s Code of Conduct, breaking HackCU’s Code of Conduct, or other unsporting behaviour.
After hacking finishes, teams will show their projects each other and to the judges.
You are strongly encouraged to present a demo of what you have built. Pitches or presentations are discouraged. You are not judged on the quality of your pitch or the quality of your idea. As you are judged on what you built, you’ll only hurt yourself by not showing a demo.
You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. It’s okay if you didn’t finish your hack—that happens all the time! Completion is only one part of the judging criteria, so you might still do well. Also, demoing is not just about the competition. It’s a chance to share with others what you learned and what you tried to build—that’s what hacking’s all about! In the case that you don’t have anything to demo, you can give a presentation about what you tried and what you learned. Hearing what other people learned is interesting and inspiring for other attendees.
Teams will be judged on these four criteria. Judges will weigh the criteria equally. During judging, participants should try to describe what they did for each criterion in their project.
- Technology: How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go “Wow”?
- Design: Did the team put thought into the user experience? How well designed is the interface? For a website, this might be about how beautiful the CSS or graphics are. For a hardware project, it might be more about how good the human-computer interaction is (e.g. is it easy to use or does it use a cool interface?).
- Completion: Does the hack work? Did the team achieve everything they wanted?
- Learning: Did the team stretch themselves? Did they try to learn something new? What kind of projects have they worked on before? If a team which always does virtual reality projects decides to switch up and try doing a mobile app instead, that exploration should be rewarded.
These criteria will guide judges but ultimately judges are free to make decisions based on their gut feeling of which projects are the most impressive and most deserving.
It’s important to note that these judging criteria do not include:
- How good your code is. It doesn’t matter if your code is messy, or not well commented, or uses inefficient algorithms. Hacking is about playing around, making mistakes, and learning new things. If your code isn’t production ready, we’re not going to mark you down.
- How well you pitch. Hacking is about building and learning, not about selling.
- How good the idea is. Again, hackathons aren’t about coming up with innovative ideas. It’s about building and learning.
- How well the project solves a problem. You can build something totally useless and as long as you’re learning and having fun, that’s a good hack! Sometimes a pointless project is one of the best hacks!
So don’t worry about coming up with the next big idea or building the next Facebook. You’ll have plenty of time for that outside the hackathon. just focus on learning, having fun, and making new friends. At the end of the day the skills you learn and the friends you make might lead to the next big thing—but you don’t have to do that to win a hackathon.
The competition is just a part of the hackathon. To make the most out of the event, try something new, teach other people, and make new friends!
Happy Hacking from the HackCU Team!