This semester the COMP110 undergraduate teaching assistant team is excited to introduce the first-ever COMP110 Hackathon. This will be a fun event to hang out with classmates and the COMP110 team for an all-night hacking session on open-ended final projects.
There are two options for a final project in COMP110:
Want to do both? That's perfectly acceptable, too! Unfortunately, to keep things fair to all, there's no extra credit involved for completing both. Only extra street cred.
After workshops complete, we will break into the lobby to begin hacking on hackathon final projects. Reminder: we will not be able to assist with PS6 – Compstagram.
1. Come up with an idea! Don't know what to make? Try grabbing a team member or chatting with a classmate and brainstorming!
2. Before 12am -- Once you have an idea of what you would like to try hacking on as your final project, submit a conceptual help ticket in the office hours app and come tell us a bit about it! After doing so, you will be given an "opt-in code" and should complete the opt-in form found here: http://bit.ly/hack110-optin
3. Hack! Try to complete or make a substantial dent in your project at the hackathon! Staff will be circulating around to try and help push past road blocks or brainstorm workarounds. Google and StackOverflow are your friends for solving problems you've never tried to solve before. Starting from the "zero support code" instructions of Chat110 (found here), you can kick start a JavaFX application and get moving!
4. Once you've reached a point of demonstration of your idea you should work on the web page for your project using the instructions Dong covered at the workshop on setting up a Github Page linked to from here.
The requirements of the project page are:
5. We will send a link to everyone who opted-in on Wednesday for a final project submission. It will basically be a form for letting us know the URL of your GitHub page. Only one submission (and one GitHub Page) on this form will be required per team, but each of you is encouraged to setup a GitHub page individually for practice.
Not meeting your complete vision for the original project is completely acceptable, but you should have code that runs and represents a body of work achievable through working on it during the Hackathon (~8 - 10hrs or more).