Celebrate the arrival of spring (whenever it actually arrives) by hacking with MadHacks and WACM!
Join MadHacks and WACM and celebrate the arrival (we hope soon) of spring by trying something new, enhancing skills you have, putting what you've been learning in class to good use, or just having fun hacking. You have 12 hours, what will you build?
Doors open at 8:30 am.
Hacking begins at 9:00 am.
- There will be some quick announcements followed by a short presentation about the Exis platform prize
- After the announcements and Exis, come to the front of 1240 if you're looking for teammates
- Exis will host a tech talk on the Exis platform at 10:00am
- We do have vegan and gluten free options, please let us know at the hackathon if this applies to you
- Breakfast 8:30am-10:00am Donuts from Greenbush Bakery and coffee
- Lunch 1:00pm Capriotti's
- Dinner 5:30pm Taj
Hack submissions are due before 9:00pm.
- Open only to UW Madison undergraduate and graduate students
- All majors are welcome to participate
- Participants must be registered and physically present at the event on April 16 2015
- Participants must be 18+
- Teams may have 1-4 members
Even if your hack isn't "finished" you should still submit it for judging. Build the best hack you can, that best demonstrates your idea, given the short time you have to build it. Your submission should include
- A 'functional' prototype or your software or hardware
- A demonstration video (if applicable) showing your hack in action
- Links to website and/or GitHub
- Design documents, sketches, illustrations of your idea
- An explanation of your hack-- why did you choose this project to build today?
- What are your future plans for your hack?
If you use Exis.io for your hack, make sure to submit your hack for that particular prize
Submit your hack well before the deadline-- you can update it until the deadline
How to enter
- Register in advance at https://madhacks.org/springfever/
- Note that seating is limited (event is in CS 1240)
Software Developer / Epic Systems
Technical Evangelist / Microsoft
Electrical Engineer / Sector67
Chief Technology Officer / 5NINES
How complete is the hack, both in terms of being operational and compared to the proposed design?
Does the hack properly and efficiently offer a solution that addresses the idea or problem at hand?
Is the hack based on another application, or is it a completely original idea?
Did the team clearly define what problem or idea they decided to tackle? Did they illustrate how they approached the solution, and what hurdles they had to overcome?
What new skills or knowledge did the team members acquire? Did they learn a new language, or use a new framework for the first time? Did they apply skills and knowledge from class work?
What's next for the hack? Are the team members planning to continue working in it and improving it?
Degree of difficulty
How ambitious is the hack, given the limited time to build it? Is the hack far too large in scope, or is it too small in scope? Is this a hack that can be legitimately created from scratch in 12 hours?
When you look at this hack, does it have a style all its own? Does this hack do what it does in an especially elegant way?