After organizing 12 Coding Battles, this was only the second time that we had the chance to work on a “Code for Good” theme. It won’t be the last.

The first time it we played with Google Maps API and the list of defibrillators in Belgium to create an app that would locate the closest to your current position.

This time, it was slightly more futuristic: “The connected future of Healthcare”. We loved it.

It’s true, the aim of the game was a (very) simplified version of what it could be in reality

Still, the process of shaping the game and its rules, talking to health professionals, finding the real data and running feasibility tests was very exciting.
Even if it was only a game, it feels nice to work for a good cause.

And who knows.. it might inspire participants to continue to work on such topic.

Fun at EnCo with the Coding Battle

The evaluation method, a challenge in itself

As usual making the game fit in 2-3 hours was a real challenge. But the hard part this time was more about find the right evaluation method and how to implement it.

In real-life, there are many metrics and constraints that one would have to take into account:

  • Are patients cured or not?
  • How much time did it take to cure them?
  • How well are they cured?
  • Do they have the budget for a specific treatment?

After a couple of brainstorming sessions (health is a touchy topic), we decided to take the number of patients cured combined with the overall health of patients.

The overall health of patients would be calculated based on the time it took to cure them and how effective each treatment had been in the process.

Working with EnCo

Our first encounter with EnCo was at the VR Hackathon in Brussels.

They launched their EnCo Marketplace recently and have been working on new API integrations. They want to raise awareness about what they’re doing and build a strong brand for EnCo among the developer communities.


Rapidly, we saw our shared interest, and started envisioning how we could start working together. A few weeks later, we were announcing the Coding Battle “The future of connected Healthcare”.

EnCo wanted a theme that fit its values and the technologies that they are offering.

EnCo is a platform by developers for developers. No doubt they were super motivated to make this event a success.

They directly supported the idea of buying IoT devices (20+ Wipys and Raspberry Pis) and were very enthusiastic about creating a thrilling experience for developers.

We decided to organize the Coding Battle inside their office so that participants would get a better feel of what EnCo is: what it looks like, how they work, who they are and what’s the atmosphere inside the team.

office EnCo

How it happened

We were not the only one happy with the “Code 4 Good” theme of this Coding battle. Most community members like to work on such topics, like most of us actually.

This enthusiasm was clearly reflected during the registration phase. We even had to set up a waitlist for the event.

Eventually, we were 40+ to gather inside EnCo’s office to play around with IoT, code and data.

The Coding Battle was separated in two steps.

Step 1

The first step was about learning how to connect your IoT device to the EnCo marketplace (Cloud channel + Sensor as a Service).

Toon and Oli
Depending on their preferred language, participants could choose between Wipys or Raspberry Pis.

The integration with the latter proved a little more challenging as less documentation was available.

For this task, teams had 30 minutes. Eventually, only a couple of them managed to get it done.

The EnCo team was aware that getting started on their platform might not be as straight forward as they might have wished.

The Coding Battle was a good test to see if it was worth spending time and efforts in improving the on-boarding process.

The results and feedback confirmed that hypothesis. No doubt that we’ll be seeing improvements on that side in the coming weeks.

Step 2

After a well-deserved break, the second part of the evening could start.

Pizza time

Participants would have to play around with code and data to build an AI that would cure as many patients as possible.

As always, they would get a boilerplate. This boilerplate had a sample AI that they would have to test, tweak and improve.

If you want to read more about the details and the rules of the game, here is the page of the Coding Battle.

Conclusion

In the end, it’s Dries & Juul who made it to the top of the Scoreboard. Congrats to them! They each go back home with a Raspberry Pi 3 and a bottle of champagne, offered by EnCo.

If you weren’t there for their live explanations, go take a look at their github repo. You’ll find the explanation of their strategy and of the solution that they came up with.

Winning team

Funny enough, the runners up were not 1 but 2 teams. They had exactly the same score (6 decimals…) and therefore had the exact same implementation. That was unexpected. Again, EnCo rewarded them with a Wipy for each team. Congrat to them.

2 teams as runners up

New formats, new locations and new Coding Battles coming up! Subscribe to our newsletter to stay up to get all the latest news and events.

Wish you a great end of the year season. See you next year!