Welcome to the spring hackathon you've always wished Berkeley had! Soda Hacks is open to everyone, with free delicious food and awesome prizes.
Come join us for 18 hours of caffeine-fueled hacking and learning! Prizes include monitors, Zeiss VR One+ headsets, keyboards, and more.
- 5:00 pm - Dinner, Networking
- 5:30 pm - Opening Ceremony
- 6:00 pm - Hacking begins!
- 8:00 am - Breakfast
- 12:00 pm - Hacking ends
- 12:00 pm - Lunch
- 12:30 pm - Poster-session style judging begins
- 1:15 pm - Finalists present
- 1:45 pm - Final judging
- 2:00 pm - Prize distribution and conclusion
Saturday, April 14th
Sunday, April 15th
Workshops & Panels
Judges & Speakers
- Andy Ju - Worldwide Sr. Product Marketing Manager, Nvidia
- Caitlin Bigham - Ecosystems Manager, Facebook
- Heather Browning - VR Game Designer, Pear Therapeutics
- Ewan Johnson - CCO, Arcturus
- Victoria McClune - Creative Director, McClune Design, Inc.
- Csilla Andersen - VR Producer
- Rabi Gupta - CEO, Eva Bot
- Damon Hernandez - Product Manager, Samsung Research America
- Prizes include Muse, FitBits, Zeiss headsets, mechanical keyboards, Leap Motions, and more!
Who can attend?
- Any enrolled UC Berkeley student - of any year or background - may attend!
What can we make?
- Anything you want! This year, we're encouraging VR / AR-related hacks.
How are applications chosen?
- We will be reviewing each application on a case-by-case basis.
Are teams allowed?
- Yes - and they are highly encouraged! We will limit teams to a maximum of 4 people.
Will equipment be provided?
- No, please bring your own computers and preferred accessories.
- VR headsets (Oculus) will be loaned out for the duration of the hacking phase. These are available only first-come, first-serve.
Is this free?
- Yes. This entire event (minus transporation) is free for all hackers thanks to our sponsors.
What do I bring?
- Please bring your valid UC Berkeley student ID (Cal 1 Card), plus any electronics and chargers you may need.
- We also recommend bringing some hygenic products, a water bottle, a blanket, and anything else for comfort.
I have a question!
- Please post the question on the Facebook event page.
- If you would like to sponsor this event, contact firstname.lastname@example.org
All code written must be written in the 18-hour period, or explicitly flagged as written beforehand. Making significant use of pre-written non-framework/non-library code is strongly discouraged.
Libraries are fine, and anything reasonably called a "framework" should also be fine. Improvements to a library may not be considered in the main body of a work if they are merely incidental to the project, rather than a major component. Non-coding design pre-work and product development is acceptable. Fleshing out and preparation work, in general, should be no big deal.
If a project does not pass a "smell test," judges may, at their discretion, take this into consideration when evaluating the project. It is recommended that a README file be included which summarizes the work done and explains the necessary disclaimers for pre-work, libraries, etc. However, this is neither required nor scored.