Come hang out with us for a weekend at Youngstown State University. Right smack in the middle of the tech belt, we are inviting computer science, design, and computer engineering students from all over the region to join us for an awesome weekend of learning, creating, and networking.
Any student currently enrolled or was enrolled in the 2014-2015 school year from any upper education institution or high school can register at HackYSU.com .
If you're under 18: Sorry but, due to various factors, we are unable to host minors this year.
Though the focus of HackYSU is creative tech projects, hackers can create anything they want, permitting it is safe and appropriate. Fill out as much of the Challengepost submit form as possible when submitting your hack. Videos are optional.
$5,432 in prizes
Dell Venue tablets and Major League Hacking medals.
Pebble smart watches and Major League Hacking medals.
Raspberry Pi 2 Model B kits and Major League Hacking medals.
Best Designed Hack
Free year GraphicStock subscriptions.
Best use of Pebble
Best use of Amazon Web Services
Dell external hard drives.
Submitting to this hackathon could earn you:
How to enter
All participants must register before the event at HackYSU.com . All hacks must be submitted to Challengepost to qualify for judging.
Will be Announced
Was the hack impressive? Did you feel interested in the hack itself (not necessarily their presentation of the hack)? Keep in mind that the team had only 36 hours to make this project. And that they are tired.
Did the hack involve practicing or learning a skill? Did the team overcome any technical difficulties or lack of knowledge? Consider asking the team what they learned over the weekend.
How was the demo? Was the hack working - or at least in a state where the hackers could show off their idea? Keep in mind that the process is important, and that we are judging what happened at the hackathon, not what the hackers are planning to do after.
This goes towards our "best designed hack" prize. Consider asking the thought process behind the design - if any - to see how much of the design process was utilizing tools vs. custom design work. Remember, implementation is half the battle.