The current Hackathon culture is indicative of a general tech and investing culture of picking "hot" ideas made by charismatic teams over people doing true technological innovation which takes sustained, serious effort. The real innovation is what ends up making an impact, but the little prototype parties can be a good stepping stone into the industry.
Hack-a-thons need to change so that the objective isn't clear until you walk in so people have to create something on the spot.
Jacob is right, big prizes can suck. I'd love to see fewer big prizes at hackathons. Having some small stuff so people feel accomplished and valued is nice though. Jon Gottfried has a really good article about this[1].
I go to a lot of student hackathons and generally people are there for learning - not competition. They're certainly not there for "boozing up"!
And of course hackathon projects amount to nothing 99% of the time. That's not a problem. That's totally to be expected from 24 hours of hastily put together code. The value students get is learning about idea generation, working with others, managing a project, how to use the libraries, frameworks, and APIs, how to work to a deadline, how to debug, how to do version control, how to deploy, how to test and improve your work, how to present your work to others, and much more. And I don't think companies or VCs who attend really expect to find a next Facebook - they're probably more concerned with just meeting the kind of students who would rather spend a weekend building stuff instead of boozing. Furthermore, hackathons don't undermine the value of sustained effort on hard technical problems - but they can be the first step for students starting to work on technology outside of their courses.
You're all totally right that large prizes suck and pitchathons suck. Most student hackathons do a pretty good job of staying away from those (though some could do better for sure). As Jacob said, "hackathons should be about coding something cool, not winning, networking, or partying" - I've honestly never been to a student hackathon where that wasn't the case. So I'd be careful about throwing the baby out with the bathwater.
[1] http://news.mlh.io/are-hackathon-prizes-the-worst-thing-sinc...
As food for thought, there are "Consulting Case Competitions" for business school students year round, and some students decide to spend their time optimizing for winning a bunch of these one after another all around the country. I'm not sure if this is a good, bad, or neutral thing.
Student hackathons are and always will be fundamentally different from corporate hackathons because the motivations of the organizers and attendees are different. Perhaps we should be careful about offering large prizes for the reason you state but the focus is very clearly on learning and building and that's not set to change.
Maybe it's just getting old, but the idea of exhausting myself over a weekend in order to create something I'll likely never use again has lost it's appeal. Every now and then I'll be disciplined and tell myself I'm having a "hack weekend" where I'm relatively anti-social, stay at home and work on a project. It's a lot more fulfilling.
1 That's because most hackathans can't decide whether they want to be hackathons or pitchathons.
and
2 The current Hackathon culture is indicative of a general tech and investing culture of picking "hot" ideas made by charismatic teams over people doing true technological innovation which takes sustained, serious effort. The real innovation is what ends up making an impact, but the little prototype parties can be a good stepping stone into the industry.
My sense is that the market needs these type of pitch events with some type of filter. One filter is letting a group of experts at an incubator pick who you see. Another filter is having folks savvy enough to appreciate what can be gained from gaming hackathons.
One way to view this is, "If you want them out of hackathons, how do you pay for hackathons and attract the right people, and where should the pitch-masters go?"
I'm not sure ditching recruiters and VCs is the right answer. Perhaps having very technical keynote speakers helps? Or making the objective to be code reviews from famous engineers? (Instead of Google paying for expenses and a dozen recruiters, Google sends a couple very good engineers to peer review code. This is more expensive, but perhaps brings them better benefits too.) If there's no product pitch and PR, and a better alternative elsewhere, perhaps the pitch-masters will stay home?
So what to do with the pitch-masters, when there's only so many presentation slots at TC and seats at YC? I don't have a good answer for this, but it sounds like a market opportunity for someone.
Maybe it was because it was a student focused event - but I saw no evidence of cheating and the prizes were so small that it would have not been worth pre-building apps beforehand anyway.
There was a period of time -- and I hope we're over it, for the most part -- where "biggest, best, craziest, and most expensive" was the motto. It doesn't work; I've personally been to a couple of those huge hackathons and was really frustrated by the experience.
I work for an org that runs a nationwide (in the US) series of events called CodeDays that are somewhat similar in format to traditional collegiate hackathons and those are exactly the kinds of experiences we're trying to create, so we have a pretty strict limit on prize size, we only allow 100 students per city, we market to younger students, etc.
That's worked out incredibly well for us. A couple of the people profiled in this article actually got their start at a CodeDay.
(Interesting, CodeDay is also much much cheaper than these huge hackathons and we engage more students, just distributed across 30 cities.)
But remove the Grand Prize, because it makes the whole thing feel like a competition to people, and cheating / pre-building projects is unavoidable. Even the grand prize winners at Treehacks (built the robot arm, mentioned in the article) partially faked it - they were asked by the judges how much of the hardware they built before the hackathon, and they said they built all of the hardware beforehand. How much of the software had they already tinkered with / sketched out / built? Who knows.
So remove the idea that pre-building is cheating, and instead of 3 big prizes give out 50 small ones.