Hackathon by numbers (or how to win a hackathon)

The winning team spent 37% of the total time coding (i.e. working) and only 10% chatting.

Hackathon by numbers (or how to win a hackathon)

Hackathon stats: the highs and lows in figures

Since writing my Hackathon blog I have been inundated by an email asking why there were no statistics included. To address this I have done some research and can report the following interesting facts:

–          The event lasted 30 hours.

–          26 people entered, although 2 were unable to compete in the end, leaving a total of 24 participants.

–          6 teams entered.

–          The smallest team had 3 members, and the largest had 5.

–          27 pizzas and 48 cans of Red Bull were consumed during the event.

–          At least 5 statistics were made up during the opening speech.

Here is how the five teams spent their time (note the totals are different due to the varying number of team members):

Hackathon Part 2Pic1

 

So, how did the most successful teams spend their time? Let’s look at the top 3 teams: The winners (Fetch): 

Hackathonblog Pic2

Second place (The Wookiee Nerds):

Hackathonblog Pic3

Third place (RSDRM):

Hackathonblog Pic4

Coding, researching, sleeping and chatting

As a member of the Wookiee Nerds I’m proud that we spent the most time sleeping (26%) and all teams spent 4-5% of our time eating. Perhaps unsurprisingly the clear difference is the amount of time spent coding. The winning team spent 37% of the total time coding (i.e. working) and only 10% chatting. Sounds like a winning formula. A lesson for us all I think. (Although none of us spent time on bug fixing.) So there you have it. The earth-shattering conclusion is that to win at a Hackathon you need to spend more time working, less time chatting and less time sleeping. I’m sure the extra team member or two helps as well.