Preparing for a Hackathon - Simple Points to remember

Feel nervous, excited, tired, and passionate a day before a Hackathon? Well, You need not worry now! Here are a few experiences that can help you cope up with anxiety, stress, and also keep you motivated!

Remembering my first experience in a hackathon, I was all nervous and excited at the same time. Overthinking about what I should do and what not. Before this hackathon, I had a misconception that a hackathon will only involve coding for the entire day, which is why I never felt like participating until my Third Year. As a matter of fact, hackathons are not only about coding, their main aim is about problem-solving. I'm sure reading this blog will help you with your first ever experience in Hackathons.

Usually, there are a couple of stages to get selected for a hackathon. Some of which is a screening process where you need to submit your ideas and solutions to the problems given to you, or maybe they select you for the hackathon based on your resume and CV. In my case, the participants were selected on their resumes.

Let the Hackathon beginnn!

Hackathons do get hectic when it's your first time so you need to make sure you get yourself a sound sleep a day prior to the hackathon. As a fact, during my first experience, there were people all over the place, most of them were in their designated places working on their codes and presentations, some were roaming around the corridors getting as much feedback from advisors, and a few of them chilling outside and taking a nap in the common room. So you need to actually prepare yourself a day before the hackathon, that you can give your full concentration and focus throughout the hackathon.

My Team Name in one of the Hackathons

So it even gets all interesting when it comes to naming your team. My team name was "Bro Code" in one of the hackathons I participated in. Choosing a good name for the team which all the teammates agree too also acts as a problem-solving task prior to a Hackathon. (lol)

 Here are some steps you need to take care

 of before a Hackathon:

1. Know Your Goals and Objective

There are so many good reasons for actually participating in a hackathon. Are you looking to learn something new? Do you just want to make a network? Are you there to WIN maybe?

Now a Hackathon can actually help you achieve all these objectives -- maybe not all of them at once. Setting your goals well before a hackathon begins will not only help you define your objective but also help you manage time during the hackathon.

2. Build a Team for a Hackathon

You would have more control over the Hackathon if you come in with a team pre-formed with teammates with whom you are comfortable working with. A lot of people form teams where maybe the tech domain of the different teammates may differ and this may cause problems for the team during the hackathon in deciding a problem statement.  

So make sure you form a team that can work together over a particular problem statement, and also has some domain expertise which may go in hand with yours.

3. Choose Your Project Domain wisely

Mostly Hackathons already have a theme and are domain-specific. As soon as you sign up for a hackathon with your team, start brainstorming different problems you want to focus on with your team.

If the hackathon is sponsored by some XYZ company, think ways you can help their product get more efficient. Pay utmost attention to who the judges are, and use their area of expertise to actually work on your problem statement.

4. Give yourself a week to prepare! 

Once your team, idea, and objectives are decided, it's time you get to work! You can give yourself at least a week to prepare and get ready for the hackathon. Utilizing your time depends on your goals and objectives.

There to win right? Start creating your pitch, designs, and logos for your websites and project -- practice delivering the pitch so you can slay during the actual pitch. Maybe you're eager to learn a new technology or framework? Start diving into tutorials and build mini-projects to get yourself comfortable with the technology.

Most of the hackathons state that all the coding has to be done at the event itself, non-coding work can be taken care of well in advance though.

5. Prepare a proper Time-Oriented Plan 

Hackathons typically last around 24-36hours and this time will eventually fly especially if you want time for meals and naps!

Make a proper plan on who on your team will work on what, and how long will he work on it. Make proper plans focusing on the time the task will take.

Bugs and errors may creep up anywhere. Deciding in prior how much time you are going to allot for the different parts of your project and when to move to plan B, will help you ensure that you have something to pitch.

6. Take Care of your Health 

Hackathons are designed to be intense. Basically, you are locked in a room, with a deadline, surrounded with snacks, and you can't even sleep(If you really care). The environment is hyper-stimulating, but make sure you don't push yourself to go beyond your health bounds.

Try to eat healthily and make sure you schedule a nap to get boosted up back again. Taking care of yourself will ultimately boost your productivity and focus. 

The only source of knowledge is Experience - Albert Einstein