Hackathon Diaries: Royal Hackaway
January 24, 2018
First part in our series of trips to hackathons around the world
What is the difference between a hackathon in Finland and one in UK? I wanted to find out how hackathons around the world differ and decided that this year I’m going to travel to different hackathons around the world. About a week ago I did my first little research trip. to Royal Hackaway, Royal Holloway‘s first student hackathon. Here’s what I found out.
Early Saturday morning I stuffed one day’s worth of clothes and a borrowed sleeping bag into my trolley bag, and headed to the Helsinki airport. The flight went fine, although I did get a nosebleed the moment the wheels touched the landing strip, and dirtied the only hoodie I had with me (having bloodstains on your hoodie in hackathon shows character). After I had landed and stuffed a sizable amount of paper cloth in my nose, I made my way to the bus. There I played a round of “spot the tourist” with the bus driver before jumping on board. At this point I had spent about five hours traveling to this hackathon.
Once I reached the campus of Royal Holloway (”The most beautiful university in UK”), I snapped a quick picture of the premises and composed a Facebook post (I got like 20 likes, baller yeah). After that I made my way to the building where the hackathon would take place, received my badge and lunch vouchers, and walked into the auditorium where the show was about to start.
Theme of the hackathon turned out to be open data, a relatively original theme⸮ Once the welcoming speeches ended, we moved to another room and started hacking. No team formation, no nothing. This is a thing I found a little stupid because it felt that organizers did not consider that there could be people running solo (like me for example). I was able to force myself into one team after bragging how many hackathons I’ve won (14, not that I’m counting or anything).
Our team spent around two hours getting to know each other and coming up with an idea to build. We finally decided to build a tool that would put all the hackathons around you on a map, show the prizes, and provide fare estimates for flights (hey, Major League Hacking, the map part would be good addition to your site as well). After this it was time to decide who would work on what and what kind of stack we would use — we chose Vue.js, which was positive surprise.
“…no offense but I thought you were shit!”
What was my part in team? I started by reading a little Vue.js documentation in order to start building the frontend. After a rough start I was asked to build a HTML mockup instead. This I did for maybe 20 minutes, before I once again asked to do something else, this a photoshop mockup. Reason for constant pivots was my team’s distrust in achieving in these tasks; or at least achieving them in a way that would helps us win this thing.
Once I was done with the mockup I showed it to my team mates, half expecting to get disappointed looks. To my surprise, I got a heart warming “dude this is really cool; no offense but I though you were shit!” compliment on my mockup. After that our work together went really smoothly and we managed to build most of the app during Saturday. Sunday we spent fixing and rewriting everything we had written the day before.
I got a pretty solid 4 hour sleep during the hackathon which you might consider to be a lot, but you are wrong. Well, first because little sleep can do wonders to your cognitive functions. In hackathon context you should aim around 50% of the sleep you get on an average night, to continue functioning at about average performance. Second reason is, because I’m old and weary I need my sleep (26, which was about 6 years over the average age of this hackathon).
Submission deadline was at 12, after which it was time for presentations. Judging by the presentations most teams seemed to consists of first timers, which is always cool. Hackathons need fresh blood.
When it was our time present, we got to stage and presented our project. We had actually created a two solutions: an API that gave us hackathons and webservice to used that API. We had to remove the fare estimates for flights because it turned out Google’s API and Skyscanner’s API aren’t open anymore. You can find a more detailed explanation of the project here.
Then came time for the prizes. I’m quite sure that the judges decided to give prices to other teams instead of giving all of them to us, to keep up the morale. After all, our hackathon submission was a masterpiece. The first place went to a solution that converts video and audio files to text summaries, with the help of ML, making it easier to study. I’m a bit sad that my personal favorite, a web site which tells you if Trump thinks your country is a shithole, did not win. It had all the potential to be a disruptive tool in international politics.
I want to say special thanks to the organizers of Royal Hackaway. I enjoyed the event a lot, especially the atmosphere. But I do also have small suggestions that could make the event event better. First, some kind of a team formation activity would make it easier to get started. Second, a more defined theme, or a challenge to solve that you advertise before the hackathon, could also make the hackathon more marketable.
I want to also thank my teammates, working with you during the weekend was a blast! I was also really impressed with your skills. I hope to see you in Start Hacks in Switzerland.