5 ms·
A week-long hackathon, sounds fun!! I think the most important thing to do for a hackathon is often to set and agree with the team on what will be presented at
by raymondgh 6y ago
A week-long hackathon, sounds fun!! I think the most important thing to do for a hackathon is often to set and agree with the team on what will be presented at the end. I emphasize presented and not built, because the biggest impact you can have is to influence future activity, not to solve all problems in a week. The story you tell with your presentation will be determine the future of the project, and the week's work should be prioritized based on what will best support the story you want to tell.
That said, it can also be really fun to set the goal of actually solving something with the time you now have, and showing it off. Just try to avoid a compromise where you build something 50% to production and tell 50% of a compelling story... you'll end up with leftover, low-priority homework that doesn't fit into anyone's schedule
- thirtythree 6y agoI've never taken part in a Hackathon but I thought it was all about building something. Creating a story seems very much like fluff. That's not something I would be interested in
- iovrthoughtthis 6y agoThey started as one and the same but as in all multiplayer games, the meta evolves. As hackathons started giving away bigger and bigger prizes the participants more and more join to won said prizes. The Judges only get to judge what you present, so what you present becomes the most important aspect of the hackathon. You don’t need to build a solution to present it. And here we are.
- karmakaze 6y ago> build something 50% to production and tell 50% of a compelling story This seems like exactly what a hackathon should be, a quick hack, proof-of-concept, prototype, etc that you can use to tell the story of what it can be when done to 100%. What's the point am I missing here?