Content
@
0 reply
0 recast
0 reaction
Nico Gallardo 🍄
@nicnode
HOW TO FAIL AT A HACKATHON This @ethglobal Brussels Hackathon was different. I was a mentor for the first time and I absolutely love the experience. Here's a thread of the 7 biggest problems teams face and how to overcome them. Spoiler alert: The problems weren't technical.
4 replies
4 recasts
24 reactions
Nico Gallardo 🍄
@nicnode
1. No clear goal will lead you nowhere Most teams want do everything: be a finalist, win many bounties, make a fully fleshed product, etc... But there's only so much you can do in a weekend, and many of them are not compatible. For example, if you focus on integrating too many bounties, you probably won't have the creative freedom to build a finalist project).
1 reply
0 recast
2 reactions
Nico Gallardo 🍄
@nicnode
To solve this, simply pick 1 goal, and put the others as secondary priorities. Here are some ideas and => their focus. - Build a (creative) finalist project => working MVP + narrative - Hunt for bounties => prioritise technologies that fit your idea and keep adding them - Work on (a feature for) a long-term project => get feedback from partners and mentors, seek potential grants - Hiring => try to replicate the roles of the real project you're hiring for
1 reply
0 recast
1 reaction
Nico Gallardo 🍄
@nicnode
2. Too many ideas, too little focus It's good to be ambitious at a hacakthon, but the problem comes from underestimating the amount of work you can do in just 36 hours. Stop adding more features, focus on an MVP and create a list of priorities (especially if you're bounty-hunting). You'll likely only manage the #1 prio ones.
1 reply
0 recast
1 reaction
Nico Gallardo 🍄
@nicnode
3. Too caught up in details without an MVP Many times I was approached with questions around finding loopholes in tokenomics, how to make it all completely decentralised, etc... all this without having an idea of the MVP. Solution: Don't be a perfectionist until you have an MVP idea you can ship in 36 hours. Focus on the most basic features, understand the potential flaws and explore them only if you have time at the end. Be transparent about them in your presentation.
1 reply
0 recast
1 reaction
Nico Gallardo 🍄
@nicnode
4. Bad team communication Many teams ended up fighting or with a broken product because they failed to coordinate. Understand the roles of each member of the team, and make sure everyone manages expectations. Try to base them on past work so you know where you'll need support.
1 reply
0 recast
1 reaction
Nico Gallardo 🍄
@nicnode
5. Not seeking support early on My initial shifts were empty af. The night before submission, we had a line of hackers asking for help. Don't be afraid to ask questions early on. Some things will save you hours of work by simply asking a partner or a mentor to point you in the right direction. That will also give you extra points when presenting because the judges will know you already!
1 reply
0 recast
0 reaction
Nico Gallardo 🍄
@nicnode
6. Getting stuck with a problem Despite not being technical I was able to solve tech issues by simply being a "tech therapist" lol. Hackers would tell me about their problems and find the solutions themselves. Sometimes you simply need to go talk to someone, take a walk, a nap or even shift focus for a bit and the problems will be "magically" solved.
1 reply
0 recast
0 reaction
