Every other year we have a company retreat where people from all over the world travel to California for a series of meetings and team building activities.
This is a very unique opportunity for us and we're always thinking about ways to maximize it. This time we decided to organize another internal hackathon. That way participants could finally put a face to a GitHub user and have the chance to interact with people they never worked with before in a smaller, fun-setting environment.
The idea of this article is to tell the story of how we made this happen and hopefully help you to organize a similar initiative.
For lots of developers participating on this hackathon is amazing! It's a whole day where you can stop whatever you're doing, get paid to build whatever you want, have free food, and in the end, get some prizes.
But not everybody likes to write code in a fast pace, not everybody likes to compete with others, and not everybody likes to stay in the office until late. You must respect that.
That means our first step was to build a site for people to register and explain how all that would work. You know, rules, expectations, agenda, etc.
At 8:30am participants started to arrive.
We began the day by asking them to write ideas on a piece of paper and come in front of everybody to pitch their proposals. Our only instruction was:
Describe what you wanna do and what are the resources you need to make it happen.
The recruiting process was very organic, but we encouraged them to choose people that didn’t belong to their usual departments and regions. We also wanted to foster open source development, that means every project had to be hosted on GitHub.
Once all teams were formed, it was time to start developing the ideas.
Some people are very competitive so they began to work frenetically whereas others were going slowly. You can't really interfere with how people work, but you can definitely influence and stimulate a different kind of environment. That's why we put on very loud music to shake things up and a huge countdown to remind them that time was ticking away.
From time to time, I’d visit teams to check how things were moving.
Acting as a mentor, facilitator, or simply giving an outside perspective is crucial to a team's success.
Food needs to be served throughout the day, however we did it in such a way that was not intrusive and didn’t cause too many distractions.
In our previous Hackday, we decided that we didn't want to have one single winner. We wanted them to feel like they accomplished something and were rewarded by this. That’s why we kept the same four categories as before.
Best Technical Achievement — Did the participants solve a hard technical problem? Did they get a working demo completed within the allotted time?
Most Impactful Project — How does this changes the life of developers, employees, clients, partners, or end-users?
Best User Experience — Is it easy to interact and understand? How do you feel about using such it?
Most Innovative Solution — Could this be a radical innovation or a meaningful new take on an existing product or service?
The winners would get a special mug and all participants would receive some nice stickers and t-shirts.
At 6pm everybody had to stop coding and move to the presentation area.
For “Best Technical Achievement”, a team who built a home automation system using Raspberry Pi. They basically collect sensor data like temperature and humidity, then use WeDeploy to store that information. They also built a mobile app and web interface to display that data.
For “Most Impactful Project”, a web application that fetches JIRA tickets and generates release notes for you. This is a challenging problem to solve because it involves a big amount of tickets, but they built it in a way that was easy to read and digest.
For “Best User Experience”, a voice activated web app called Chicken Hands. The idea is to allow you to navigate through a recipe while you’re cooking. So you can hear pieces of a recipe and trigger commands using your voice like fetching the list of ingredients. They also used WeDeploy for hosting.
Finally, for “Most Innovative Solution”, a mobile app that calculates the traffic to work and auto-adjusts your alarm based on that traffic. That way you'll never be late to work again.
But who decides who wins?
Well, we invited a special group of people to be our judges, that way we would have very different perspectives from different fields and cultures.
- JR Houn (Lead Senior Test Engineer in North America)
- Vitor Fernandes (Design Coordinator in Latin America)
- Bryan Cheung (Co-founder & Chief Executive Officer)
- Chema Balsas (Principal Frontend Engineer based in Europe)
This was not a only one man's work, many people made this possible, and I'd like to say thanks for everybody that helped organize this thing (specially Joshua Kuo) and all the participants who worked so hard on their ideas.
What about you? Are you planning to organize your own hack day? Any suggestions on how we can improve the next one? Feel free to leave a comment and share this with your friends!
Stay up to date
My email list is the best way to follow all the work I'm doing. Sign up below.