Project Data Hack

Project Data Hack
20th October (evening) - remote
21st October (all day) - Google London, 123 Buckingham Palace Rd, London SW1W 9SH

At Hackerthon.AI our mission is to champion and elevate women, ethnic minority, differently-abled and LGBTQ voices in technology - diversity and equity is good common sense and excellent business sense.

Code of conduct

1. You must treat all team members, competitors, judges, coaches, volunteers, etc, with respect and courtesy
2. Hackathon teams will be a maximum of 5 people
3. All prizes are to be shared between all team members
4. Teams can of course gain advice and support from organisers, volunteers, sponsors, and others.
5. All work on a project should be done during the hackathon.
6. Teams can use an idea they had before the event.
7. Teams can work on ideas that have already been done.
8. 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.
9. 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.
10. Teams can be disqualified from the competition at the organisers’ discretion. Reasons might include but are not limited to breaking the Competition Rules

Submission

Please ensure your any presentation videos, code and data are all in a zip file when submitted.

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!

After hacking finishes, pitches will be reviewed by the judges and winners will be informed by 28th October.

Judging criteria

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?
• Design: Did the team put thought into the user experience? How well designed is the 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?