Thanks for coming out!

The teaching staff of 3157 would like to thank all of you who came out to the hackathon. We all had a great time helping, teaching, and learning and hope you did too. The event was incredibly well attended and we were excited to see so many of you stick around to the very end. Happy hacking!

• 
• 
• 
• 
• 
• 

What was it?

The 3157 Hackathon was an optional hackathon intended for students and alumni of the w3157 class. Throughout the night of October 25th, from 9pm-5am, in Carlton Lounge in Mudd, at Columbia students worked on two big assignments from the class. Alumni and TAs were on hand to help students with these assignments.

This hackathon isn't just a homework programming session, it's also an open learning environment. Whether you're a hackathon veteran or this is your first time, stop by. Representatives from Women in Computer Science (WICS) will be on hand to talk about their individual experiences in the field. If you're a Barnard student who would like to learn more about what its like to be a programmer, or what a hackathon is like, do come by as well.

Aside from all the awesome people, we'll also have pizza and drinks to keep you fueled all night, tasty treats from GitHub, 3157 swag, and swag from our sponsors!

What do we do there?

• Current students: work on lab4 or lab5, or help your classmates
• Former students: help out current students on lab4 and lab5 (while also hacking on your own projects!)
• Everyone: hang out, eat pizza, talk, listen, laugh, sleep

To be totally clear...

1. Attendance is not required. It's completely optional. It's totally understandable if you have better things to do Friday night than geeking out all night
2. If you come, you don't have to stay all night. You can come and go as you please
3. At that time, both lab4 and lab5 will be open for submission. You can work on either.
4. During the hackathon, we will have a very loose collaboration policy. You can look at your classmates' code to learn or to help. You can sit down with someone else and try things together. All I ask is for you to make a genuine effort to learn or to help. You can list the poeple you have collaborated with in your README to make sure that your code does not trigger cheating detection.
   • Additionally, if you wish to set up a Github repo for yourself and your partner, the repo must be private. GitHub offers free private repository to students, but it takes a few days to process, so make sure to sign up before the hackathon.
5. The hackathon would also be a great opportunity for you to learn from your savvy TAs and classmates about some of the extra stuff that will enrich your shell experience—nifty .bashrc setups, vim/emacs setup, VirtualBox setups, using GDB, etc.
6. For lab4 you may optionally work in pairs, with an appropriately more complex set of tasks for pairs compared to individuals. The hackathon is a great place to work with your partner! More details in the lab4 directions.

Sponsors