Carleton University's cuHacking longest running student-led MLH hackathon in Ottawa.
Students come to Carleton University and spend 24h in a team to take a project from the drawing-board to reality.
cuHacking is an annual student-run MLH hackathon, where 400 students come to learn new skills, make new friends, and create industry connections. We want to create an environment where students are able to overcome the initial hurdles when learning new skills / tools, where they are free to ask for help and guidance. We want to give STEM students the opportunity and resources to apply the skills they learned in class on real-world projects, and get experience starting and finishing their own project.
$2,150 in prizes
Four AdaBox will go to the first place team. The box has all the parts you need to build just about any IoT project!
Virtual Reality Headsets
Four Samsung Gear VR sets will be awarded the members of the second place team.
The third place team will receive Four TrueFree wireless headphones.
Four Invison Subscriptions will be awarded to the winners for the Best UI/UX Hack.
Best Domain Name from Domain.com
Raspberry Pi & PiHut Essential Kit for each team member
Best use of Google Cloud Platform
Google Home Minis for each team member
Best IoT Hack Using a Qualcomm Device
410C Dragonboard for each team member
Snap Kit Prize
Use Snap Kit's web or mobile SDK in your hack. Each winning team member will receive a pair of Spectacles by Snapchat or another awesome prize.
4 x $150 Best Buy Gift Cards
This goes to the winners of the Innovapost Challenge for best native mobile application.
This goes to the winners of the InGenius Challenge for Integration of Amazon Connect API.
This prize is provided by the School of Computer Science for the best High School Hack.
Submitting to this hackathon could earn you:
Blackberry / QNX
cuHacking 2019 Award Judging
The goal of the hackathon is to encourage learning and overcoming obstacles. A winning team should have a novel idea that required the team to learn new skills, to create a cohesive and functioning final product.
A project should be a new idea, not simply a rehash or tweak of a winning project they saw at another hackathon (e.g. a QR code inventory system that uses AWS).
How much Grit did the team show when completing their project; did they give up on their idea and decide on an easy project when they encounters setbacks? How did they try to overcome their hurdles?
How advanced is their project? Did they create a simple command line application, or where they able to create a multithreaded frontend and backend? This should be subjective, based on the hacker's level of experience.
The goal is have a product that works in 24 hours. A complete project with a small set of features is much better than an incomplete project. A project with a small subset of advanced features is much better than a project with various simple features.