2nd annual hardware hackathon at Columbia University!

MAKECU is a new initiative started by members of Columbia’s IEEE Student Chapter. The first MAKECU hackathon will take place at Columbia University on the weekend of February 28 - March 1 over the course of 24 hours. Participants will have a large selection of hardware and tools to create their hardware hacks. They will also be able to participate in workshops where professors, select sponsors, and peers will teach hackers how to effectively use the hardware and software provided to them.

We expect many of the projects to use a micro-controller base or repurpose existing hardware for unique applications. However, hackers will be encouraged to let their imaginations run wild. We will provide teams of three to four participants with hardware kits and peripherals, and participants are encouraged to request specialized hardware early on. Teams will also have access to a standard circuits laboratory bench, complete with test equipment such as power supplies and oscilloscopes. At the conclusion of the hackathon, teams will demo their projects to other attendees and judges. Finally, a panel of judges will evaluate and score the presented projects.

For more details, check out makecu.org!

View full rules

How to enter

Registration for MAKECU 2016 is closed. 

Judges

No avatar 100

Chris Rill
Canary

No avatar 100

Dan Ujvari
Atmel

No avatar 100

Tom Igoe

No avatar 100

Ben Jordan
Altium

Judging Criteria

  • Most Entertaining
    Essentially, how much fun did we have when judging your prize? Should have some element of fun or whimsy that grabs the user and engages them.
  • Best Beginner Hack
    Judged on the same criteria as "overall" category, but focuses on teams that have majority members for whom this is their first time working with hardware.
  • Overall First, Second, and Third
    Foremost, projects should demonstrate that they successfully “hack together” a solution to an interesting problem or challenge. Also considered on usability, design, and technical aptitude. Not the number of features, but how well they’re implemented.