Ask HN: Do you attend Hackathons?

Hackathons are great for the CS undergrad who just learned how to make an iOS app. It's a good way to push yourself to solidify a skillset, especially while in school. Students don't necessarily have time to be doing side projects (although they should make time). Getting a bunch of work done in one big spurt can be very beneficial.

That being said, I personally don't enjoy them. Free food is great, but I would much rather be working on one of my long-term projects. Also, I think hackathons are targeted a little bit too much towards newbies, rather than experienced devs.

I would be considered a "hustler" under the terms offered in your post. As such, I have attended multiple hackathons as a company rep, to support friends, or just to keep up on new ideas. Yes, for me hackathons can be a spectator sport. I do understand the frustration of some hackers that build brilliant applications but fail to win, I have seen it happen. I also have yet to meet a hacker who does not think he/she should win every contest they enter. (that is funny because its true). Like everything else that grows in popularity the original goal may become less obvious over time. Is this a good or bad thing? It depends I suppose. One thing I do know is that popularity brings more attention, which brings more sponsors, which brings larger and more diverse hackathons. Hackers are the heart and soul of hackatons obviously, just don't discredit the business side too much. We kind of need each other. Good luck with your next event

I stopped attending Hackathons (and Jams) out of a principle decision. I've come to feel that Hackathons are only encouraging some of the worst aspects of the software industry. The industry as a whole has long, bad habits of encouraging "crunch work" and unpaid overtime. Hackathons are a celebration of those bad habits (and a mirror to them). The arguments pro-Hackathon point out that such events are unsustainable and you can't expect to do it every weekend, and yet you also start to see Hackathons filling up nearly every weekend in a year and people that try to attend all of them that they think they safely can.

I don't want to encourage "crunch work" and so I stopped paying attention to Hackathons entirely. Life is too short to burn so brightly on weekends for projects that mostly don't matter. I do worry that Hackathon culture encourages more bad software business cultures that think that they need crunch or can survive on crunch and that "everybody is doing it".

No, I don't recommend anyone but students attend hackathons. The first problem is they are usually badly executed with limited seating and very bad food. Secondly, no professional is going to allow themselves to be compared with amateurs. All a pro will get out of a hackathon is probably to look like an amateur and to be shown up by someone who has a lot of shortcuts up their sleeves. Thirdly, hackathons don't represent real world software development in which it can take weeks to roll out basic features. Only by working ahead before the competition do people complete hackathon projects in a short amount of time.

I only attend civic hackathons that are run by non-profits and for the benefit of non-profits. They are not a competition.

Stuff like: http://hackforchange.org/

I love hackathons and game jams. I also don't run to win, and definitely finishing them is victory.

I have to agree with some of the detractors here, though. If a major company sponsors a hackathon or game jam, I immediately get suspicious. Anything offering venture capital or business deals to the winner, I think it will be a "pitch-athon", and I've seen the winners be those with the best pitches, not to those with the best implementations or even best ideas. I've seen hackathons go sour from bad faith in prize money (see https://medium.com/@aliciatweet/the-dirty-secret-behind-the-... for one example).

Having said that, I join the Global Game Jam every year, and partake in several other game jams and hackathons. Dedicating a weekend to a play project, something I plan to never look at again, is an outlet for creativity and fun that I just can't find elsewhere. Sometimes I'm lucky and I'm so impressed with what I've done that I end up submitting to the app store, or otherwise sharing with the world, sometimes it's embarrassing and I never talk of that again. I've worked with a wide variety of people using technologies I've never used before.

The easiest way I think to prevent "hustlathon" is to simply not have prizes nor sponsors. Although I don't completely avoid hackathons of that nature (and hackathons without sponsors are rare, someone donated the space if nothing else!), it is far too common that some company wants to dictate what the technologies used are in a hackathon. Prizes that are "we will offer venture capital" also quickly lead to hustlathon. And a lot of times terms and conditions can approach the offensive.

Anyway, I think more than just students can learn from and enjoy hackathons. And all the comments focusing on the food? When I hosted game jams I didn't offer food! You aren't required to eat bad food.

I'm a CS student, and I do attend hack-a-thons several times a year. My policy is to ignore the competitive aspect. I should feel successful no matter what the judges decide.

My mindset from the beginning is that I won't work on the project at all after the 24 hours allotted. It's a throw-away project. This is really freeing. You don't have to worry if the code is messy, or even if there is a fundamental problem with your idea (game mechanics, etc.)

My goal is to pick a new technology or library to learn and build something with it. Once, I decided I wanted to learn how to use OpenCV, so I made a little game that is controlled by facial tracking. Another time, I had just bought some USB Nintendo 64 controllers, and I wanted to make a game that used them, so me and some friends made a local multiplayer fighting game. (The projects almost inevitably end up as games). Another project we made a multiplayer game with WebSockets to fiddle with lag compensation and clock synchronization. I learned a ton of distributed systems stuff in that short time. Sometimes, the technical problems take all time, and the finished game just barely counts as playable. Getting OpenCV bindings working with Java took nearly 8 of the 24 hours. Another project, using WebRTC for a peer-to-peer multiplayer game, only came together in the last hour, and stretched the definition of game so much that we won a special award "for challenging perceptions of what games can be" :).

It doesn't really matter, because my goal isn't really to make a great game, it's to force myself out of my comfort zone to learn something new. The game is incidental, really. Sometimes, the judges are looking for something more polished, or more business oriented. That's OK -- the game isn't for those judges. I only invested 24 hours into it. However, I've been pretty lucky, so far -- most hack-a-thons I've been to really celebrate true hacks.

I think one thing organizers can do is emphasize the process of writing the code, rather than the result. Ask what challenges the teams faced, the hardest bug they fixed (or didn't :). Near the beginning, try to offer workshops on different technologies, so that people can branch out and try something new. You can also offer categories of judging -- if there is only one category, it's hard to decide between an awesome business idea with little technical innovation and an awesome technical achievement with little applicability. No matter which one you pick, someone will be disappointed. But if there's a category for best game, best presentation, best app, most innovative, best technical achievement, or whatever categories you pick, then everyone at the hack-a-thon can participate however they like best, and be recognized for it.

I used to. I have made long-lasting friendships there. But I stopped a while ago.

I think that CS/Engineering students should attend a couple of events like this. Everyone should get exposed these (worst) aspects of the trade before hitting corporate world. (Stress, deadlines, team-work, conflicts, unfairness, etc...)

I only one once (the last time I attended) and that because I learned how to "play", putting more on the presentation and looks of the app than consistency or code quality. I basically made a demo not an app, and it won. This is why I stopped going.

[Edit]:

I know people that come with pre-coded modules for hackathons (especially in mobile dev), they copy-paste the codes and projects and just change a bit of the UI. They win every-time.

Unfair? Yes. But they hacked the hackthon system and they win, so good for them.