10 Tips to Win your Next Hackathon

#hackathons #girlknowstech #womenintech

Hello, everyone!

In 2016, I participated in my first hackathon ever. When I moved to Montreal, I discovered a beautiful community around technology where events happen every month. You might wonder what is a hackathon? Well, it is an event that typically lasts a day or two and brings together programmers to work and deliver a complete project during the event. If can be with software or hardware. It has nothing to do with hacking your computer.

I learned a lot from all these hackathons. SlackathonMTL was especially a bigger challenge for me and my team. This is where I learned the most about what needs to be done before and during a hackathon so that it is a successful event for all team members. I will let you read the article if you want to know all the details.

Tips to win a hackathon

Before the event

1. Prepare your Trello or PowerPoint in advance
Sometimes it is possible to prepare a few things before the event, without writing any line of code, of course! When it is possible, organize and assign each task to a member of the team. To do this, you can use a software like Trello. I already participated in a hackathon that had a marketing side: preparing a template for a PowerPoint could have been very useful that day! This step is optional. But that will give you a very good lead over the other teams. When the time comes, you will save a lot of time. Also, if you planned in advance, each person can do a bit of research in order to know or get an idea on how to do the tasks they will have to do (see next point!)

2. Find out in advance what technologies you will use
If you do this step, it can save you once again many hours of trial and error! This is what can make you win and take one step further in the accomplishment of your application. Often, during a hackathon, we choose technologies that we do not yet fully master - or not at all. It's perfect because it is an amazing opportunity to learn something new, but it's even better if you begin to learn the basics of the programming language a couple days before.

3. Install your work environment
Lately, I coded in nodejs and I realized during the event that my NPM was misconfigured. I lost at least a good 2 hours to run NPM to be able to install the dependencies of my project properly ... Do not make the same mistake!

4. Make a brainstorm and find an idea
In my last hackathon, the teams that have applied this tip are the ones that have been ranked among the best. Finding a revolutionary idea before the fateful day is perhaps the most important advice of this list. I lost MANY hours during my hackathons to look for an idea. On the other hand, at certain events, sponsors are present and can propose challenges with a prize to win. You may change your mind about participating in this type of contest, but at least you will always have an alternative idea.

5. Take everything you need to survive 24 hours
When I go to an event, I bring everything: pillow, blanket, a bottle of water and thermos for coffee as well as some snacks. Even though I never sleep, I am always very happy to have brought these objects, because I am comfortable during the night. Also, sometimes showers are available. You can then take a towel and other necessities. I also always bring several t-shirts, because when you stay awake for 24 hours to code, it's good. Also, the events actually last much longer than 24 hours, as after the coding time it sometimes it takes up to 8 hours until the judge's presentations, the closing ceremony and the announcement of the winners. My friend Kim wrote a complete list of what to bring to a hackathon, you should definitely check it out!

During the hackathon

6. Set small and achievable goals
It's very dangerous to aim too high, you could end up with an application that is not functional at all. Set very small goals. It is easier to target a small and functional product and then work to add more features. At the beginning of an event, and especially during a brainstorm, ideas can go very far and be complex. However, once the brainstorm is finished, it is important to remember that you only have 24 hours. Be realistic! You should also be aware that as time goes on, you get more and more tired. Small bugs that would usually take you 10 minutes can take 1 hour when you have been coding for 12 hours.

7. Do a lot of meetings
It is essential to be aware of the progress of the members of your team. You can rely on meal times to make these meetings, and a little more if needed. For a hackathon that starts around 9 am, good meeting hours would be: 12 pm, 2 pm, 6 pm, midnight, 3 am, 6 am, 8 am. This makes it possible to reevaluate the tasks and objectives of your application when problems come up. You will be able to decide the remaining tasks according to the time you have left since it is always necessary to provide a functional application. Also, at each meeting, set a list of tasks that should be completed before your next meeting. This is the secret in order to achieve and deliver a finished product.

8. Use GitHub for version control of your code
This may seem obvious to some people, but I still saw people being able to do a hackathon without git! If you are tired and make a mistake in your code, git will make it easier to go back and fix it. Keep in mind that you can never do too many commits! In my last hackathon, we spent 6 hours without doing any commits. This was a big mistake that we regretted at the end when we finished with an app full of bugs because of a bad manipulation of the commits! ;)

9. Take breaks & enjoy workshops for networking
A big advantage to participating in hackathons is the opportunity to learn new technologies and meet new people. To do this, it is very important to take breaks, talk to the teams around you and participate in the workshops organized! You should take some time to go talk to the sponsors of the event. You'll get some swag and network at the same time.

10. Maintain positive energy in team
It is important that all team members are in a good mood at all times. Everyone will be very, very tired at the end of the event. It's part of the joys of doing a hackathon. On the other hand, we must respect this fatigue and not dispute uselessly with our friends. If the emotions are running high, a group hug will solve all your problems (I speak from experience)!

That's it!

Do you think I left anything out? Write it in the comments section!

This post was originally posted on girlknowstech.com

Top comments (6)

Felix Sonntag • Jun 15 '17 • Edited

2 and 3 are very valuable. My friend spent the first 30 hours of a 40 hours hackathon trying to get Angular 2 running (the beta was just released). Well, of course in the end their result was very immature compared to others.
Something similar happened to me in another hackathon, we couldn't get the planned setup working. So we just stopped after three hours and tried a completely different approach...

But I strongly disagree with 1. The point of a hackathon is to do everything within the given timespan, so preparing presentation slides feels like cheating.

Also another neat trick:
Always keep a list of ideas and add new ideas every time you have one. So you can always fall back to that list.

Girl Knows Tech • Jun 16 '17

Hi! Glad you agree with 2 and 3, let's talk about 1!

I agree with you. I personally never did prepare anything in advance even if I would want to. My life is so crazy and I am running from one event to another. However, it might depend in the kind of hackathon. I mean yes, people do arrive sometimes with ideas. Of course no coding, but you can't stop your mind from thinking about what you could do, right?

I mostly included that in my post because I know some people don't consider it as cheating. I'm not even sure what my opinion is. I mean... it's not coding. It's just saying who does what. That work could even change when a team arrive at the event if they get influenced by the companies...

I would be very curious to know what is the general opinion about this. How much people agree with dispatching tasks before a hackathon and how much thinks it's cheating?!

I love your list of ideas. Because you're right. I don't know about you, but my and my teams never have any ideas before a hackathon. (That's probably why we never prepare anything anyway!) We just meet companies at the event and often end up doing a project that can fit in their contest so we have more chances to win something. It's another motivation.

Thanks for your comment !