ePages Hackathon 2016

Another year, another ePages hackathon. Spring is a nice season for hacking, isn’t it? The world comes alive, the days are longer, and our developers have even more energy… for coding 😉! But what exactly did we do?

Ready, steady…

This year’s hackathon focused on app development. Now that this was clear, we started to collect more detailed topics and built individual teams. The Scrum Masters addressed all manner of things associated with the hackathon organisation: Meeting rooms had to be booked, working spaces to be coordinated, snacks and beverages to be organised, as well as agreeing upon the final topics.

Finally, it was time for the colleagues from Jena and Barcelona to travel to ePages headquarters in Hamburg.

Prior to the event itself, some developers met in bars or clubs in Hamburg to outline their ideas, or prepare their GitHub repositories.

…go!

At 9.00 a.m. sharp our CTO Harm Behrens kicked off the second ePages hackathon. Once the agenda was presented, the developers split up into their teams, settled down, and got hacking. The following 36 hours then consisted of three main activities: hacking, teamwork, and fun. The challenge of feeding developers glued to their computers isn’t a small one. Thankfully, tons of crisps, cookies, pizza, and lemonade helped to focus on the tough tasks they came to solve.

Ship it!

After much weaving of code and pushing of pixels while having a great time together the teams presented their projects. The audience was highly impressed by those well-prepared presentations and all those polished results.

See Full Image

We saw native Android apps developed in Java, cross-platform apps for Android and iOS done with Ionic Framework or React Native, as well as Web apps. Meanwhile, some teams focused on other projects, like a REST cache layer, or a complexity measuring tool, or preparing a…

… video about this awesome hackathon!

About the author

Birgit Bader is an experienced Technical Communicator. Her heart beats for UI writing, localization, and API documentation.