4 ms·

Just semi-hosted a hackathon recently. Key elements: - good desks / places to sit and code - reliable internet - free dinner, midnight and/or 3am f

by DTrejo 16y ago

Just semi-hosted a hackathon recently. Key elements: - good desks / places to sit and code - reliable internet - free dinner, midnight and/or 3am food - healthy food in addition to junky food - some like energy drinks - don't have people pitch their ideas - have an official wiki for people to post their team+idea - tell contestants your judging criteria before the hackathon starts (and make sure judges know it) - keep presentations speedy, with a gong to keep people honest (<5mins for final demos) - have a nice big central room for everyone to code in (don't spread people out across the building) - don't require judges to give feedback after each demo Some of these are lessons learned from the New England College Hackathon (http://nech2011.com/ http://nech2011.com/).

thegoleffect 16y ago
+1 for reliable internet. One dinky router is not enough to satisfy 200 hackers. I've been to half a dozen with internet issues and it destroys productivity. Even with iPhone tethering, if we had 200 tetherers the cross-interference would make it just as bad. In addition to internet though, do not forget adequate power - electricity.
- petercooper 16y ago
  +2. At a hack day I was at recently, it took the guy next to me 10 hours to install Git (from source), Ruby (from source), download some gems and get Rails running because the bandwidth was so in and out. His bad for not coming with a properly set up machine, but still.. Good Internet can undo a lot of miseries.
DTrejo 16y ago
A few I forgot / gleaned from http://news.ycombinator.com/item?id=2240226 http://news.ycombinator.com/item?id=2240226: - if any organizers are competing, don't allow their teams to them enter - don't let sponsors bother coders (a few brief interviews and a pitch at the beginning is OK, but asking everyone to do a survey is not the best idea.) - explicitly have contestants outline what they actually built during the hackathon, or have judges go around and talk to people ala http://news.ycombinator.com/item?id=2240576 http://news.ycombinator.com/item?id=2240576. Or check git/svn logs. - have contestants list # of team members so judges can weight this into their decision (otherwise winning is super hard for 1-person teams) - discourage non-workers from attending and distracting coders

by DTrejo 16y ago

thegoleffect 16y ago

+1 for reliable internet. One dinky router is not enough to satisfy 200 hackers. I've been to half a dozen with internet issues and it destroys productivity. Even with iPhone tethering, if we had 200 tetherers the cross-interference would make it just as bad. In addition to internet though, do not forget adequate power - electricity.

petercooper 16y ago
+2. At a hack day I was at recently, it took the guy next to me 10 hours to install Git (from source), Ruby (from source), download some gems and get Rails running because the bandwidth was so in and out. His bad for not coming with a properly set up machine, but still.. Good Internet can undo a lot of miseries.

DTrejo 16y ago

A few I forgot / gleaned from http://news.ycombinator.com/item?id=2240226 http://news.ycombinator.com/item?id=2240226: - if any organizers are competing, don't allow their teams to them enter - don't let sponsors bother coders (a few brief interviews and a pitch at the beginning is OK, but asking everyone to do a survey is not the best idea.) - explicitly have contestants outline what they actually built during the hackathon, or have judges go around and talk to people ala http://news.ycombinator.com/item?id=2240576 http://news.ycombinator.com/item?id=2240576. Or check git/svn logs. - have contestants list # of team members so judges can weight this into their decision (otherwise winning is super hard for 1-person teams) - discourage non-workers from attending and distracting coders