TribeHacks will take place March 31st through April 2nd in Earl Gregg Swem Library. Teams will start hacking Friday evening after the Opening Ceremony and continue working until Sunday morning at 9 AM. All submissions MUST be made here on Devpost.
We will have a full MLH hardware lab, 12 fantastic sponsors, plenty of swag, and free food! All you need to do is come out and have a good time!
$4,700 in prizes
TribeHacks: 1st Place
TribeHacks: 2nd Place
TribeHacks: 3rd Place
Use your tech skills for good and hack online harassment! Build a software solution that can help reduce the frequency and/or severity of online harassment. Members of the winning team receive Hack Harassment Battery Packs!
Amazon Web Services - Best Use of AWS
$250 in AWS credits to each member of the winning team
Best Domain Name from Domain.com
Domain.com Swag Bags
Logapps: NLP Challenge
Details can be found here: https://github.com/ACMWM/Logapps-TribeHacks-Challenge-2017
Alixpartners: SQL Challenge
Each winner will receive a prize kit including a Nike pullover, wireless headphones, and an Amazon gift card.
Details can be found here: https://github.com/ACMWM/Alixpartners-TribeHacks-Challenge-2017
Submitting to this hackathon could earn you:
Any current college student, or anyone who has graduated in the last 12 months is eligible to attend TribeHacks.
The maximum team size is 4 people.
Assistant Professor, W&M Physics Department
Robert Michael Lewis
Chair and Associate Professor, W&M CS Department
Mobile Developer, Dominion Enterprises
How complicated is the hack on a technical level? What algorithms or frameworks are used? Were technical challenges solved in an elegant way (given the time limit)?
Is the hack creative? Is is a new idea, or maybe a new spin on a tried and true formula?
Is the hack intuitive? Could someone use it without a ton of explanation? Is the hack attractive such that people would actually want to use it?
Does the hack solve a real world problem? Could it be viable in today's market?
How many of the teams goals were actually implemented? A project with lofty ideas but little implementation should not receive as high a rating as a project that has many features actually implemented.