What makes a good hackathon? As a frequent attendee, these patterns have stuck out as successful to me: 1. Set over the course of a weekend. Allows greater breadth of attendees. Not 24 hours (which is somewhat manic) but rather a more leisurely schedule of Friday: beers/pitching/team-forming; Saturday: hacking; Sunday: polish, pitching-practice, pitches, award ceremony. 2. Strong focus/process/timetable. Ensure every…
Ask HN: What makes a good hackathon?
21–30 of 53 posts
Re: Ask HN: What makes a good hackathon?
#221. Have a well defined target audience and reach out early. People make weekend plans.
2. Be very clear about judging criteria.
3. Heavy presence of organizers throughout the event. It's not always easy for newbies at hackathon's, and organizers/mentors being around during the whole thing is great motivation.
4. A good venue where people can find quiet space/at the same time space to socialize.
5. Find a good balance between cheerleading during the hackathon and people working. Sponsor events are important, but continuous interruptions do not help flow work.
Re: Ask HN: What makes a good hackathon?
#23Re: Ask HN: What makes a good hackathon?
#24Good internet connectivity.
Re: Ask HN: What makes a good hackathon?
#25personally, the latter strikes me as betwixt and between - if i wanted the competition, i'd rather enter a pure programming contest with explicitly artificial problems and well-defined judging criteria, and if i wanted to build something i'd rather be doing it cooperatively than competitively.
Re: Ask HN: What makes a good hackathon?
#26Do it on a weekend, have interesting sponsors with prizes, and make the judging/presentation criteria very clear from the start. Also attendance can be hard to estimate, not everyone will show up and not everyone will come back, plan accordingly.
Also, three pieces of advice I always give at hackathons:
1. work backwards from the presentation
2. only build what you show
3. only show the interesting parts
Happy to mentor/judge, mat@tinj.com.Re: Ask HN: What makes a good hackathon?
#27Stable Wi-Fi. Don't charge for admission. Adhere to a strict fresh code rule. Limit teams to 4 or 5. Stick to your judging criteria (fun, business, innovation -- whatever it is, be consistent from start to finish) and find non-sponsor judges to choose the overall winners of an interestingly themed challenge. Provide enough water and food for everyone. If you're hosting it in San Francisco, there are plenty of hungry people who will eat the leftovers. Have 2 rounds of presentations if there are more than 30 submissions. Have someone go around and tell hackers to simplify their ideas and explain the meaning of a weekend MVP.
Follow these and you should have an acceptably successful hackathon. If you want to be memorable though, try something new!
Re: Ask HN: What makes a good hackathon?
#28I've been to around a dozen in the past year, here's my take: Stable Wi-Fi. Don't charge for admission. Adhere to a strict fresh code rule. Limit teams to 4 or 5. Stick to your judging criteria (fun, business, innovation -- whatever it is, be consistent from start to finish) and find non-sponsor judges to choose the overall winners of an interestingly themed challenge. Provide enough water and food for everyone. If y…
Re: Ask HN: What makes a good hackathon?
#29Re: Ask HN: What makes a good hackathon?
#30I've noticed two things that have ruined hackathons for me: - People that say they have skill in XYZ, when in fact they have little to no experience in XYZ. It would be nice if I could have some reasonable confidence in a stranger's ability to be experienced in a skill they claim to have. - "Entrepreneurs" interested in getting free dev labor for their unicorn app idea. I sign up for a hackathon to have some fun and…
Honest and hard working > skills but not actually.