Inspiring stories from developers who have answered the Call for Code
Call for Code 2019 is almost over. Let's take a look at some of the inspirational developers who participated in hackathons this year.
Developers, the time is now for you to answer the Call for Code 2019 Global Challenge! Throughout this year’s challenge, we’ve seen inspiring ideas come from around the globe — including places like Bikini, Melbourne, and Cairo. These solutions are innovative in their approach to addressing natural disasters, but they also reveal the passion that so many developers have for using their talent for good.
Here are a few highlights:
Innovative fire solutions from the 42 School hackathon
From every event, developers have stepped up to create innovative solutions that could help save lives. At the 42 School hackathon, we saw two impressive solutions. Hackathon winner Kenji Kato built an IoT weather station called Emergency Info Guide that measures and predicts wildfire movement and sends the data to first responders to aid them in their rescue efforts. Kenji takes advantage of the IBM Cloud by implementing Node-RED and an IoT codebase onto it. Kenji describes his device as a “data spike” as a self-contained, micro weather station designed to help firefighters during wildfires.
The hackathon’s second-place solution also focused on wildfire. In developer Roy Stahl’s case, it was personal. Stahl lost his home in a wildfire in 2015. His team developed the FREE Sensor, which stands for First Responder Emissions Exposure. The hardware/software solution is a sensor that firefighters would wear that would provide real-time data on smoke exposure and inhilation. With the power of Watson and IBM Cloud, FREE analyzes that data and provides a score to each firefighter that assesses their health and output in the field.
Interesting ideas from IBM’s own internal Call for Code challenge
IBM held its own Call for Code challenge for internal teams again this year. So many great ideas have already come from this competition. We are very proud of the IBMers who stepped up to answer the call with their potentially life-saving solutions. While we can’t highlight all of them, here are few interesting ideas that our own developers came up with:
- Team TriaMon – An end-to-end electronic triage solution, where patients receive an IoT emergency sensor strap that actively monitors the patient’s health status. This live information will also be transferred to the cloud and visualized in the emergency control room.
- Personalized Disaster Assistant – A mobile application that helps people who are affected by natural disasters by recommending personalized actionable tasks before, during, and after a disaster.
- SmartQuake – People wearing the sensor-enabled SmartQuake vests will be located faster. In addition, this team developed an AI-powered virtual assistant, Richter, to help people prepare before an earthquake.
- DisasterPicUp – DisasterPicUp is designed to facilitate disaster cleanup by allowing the community to participate in the identification of individual sites that are in need of cleanup after a disaster has occurred. Cleaning up after a disaster happens is an important part of the process to ensure communities build back better and healthier.
Five days and counting
At the time of this publication, you still have five days left to ideate, finesse, and submit your Call for Code 2019 solutions. Use one of our curated Solution Starters to help you get started:
- Building Back Better to Reduce the Impact of Future Disasters
- Improving Flood and Drought Prevention and Response
- Humanitarian Protection in Times of Disaster
- Accountability and Centrality of Protection for Affected Populations
And check these other tips and tricks to make sure your solution is in tip top shape:
- Top tips for making your Call for Code submission stand out
- How mentors can benefit you and where to find them
- Letter from Call for Code CTO: Answer the call in 2019
Make sure to also check out a livestream on our Twitch channel tomorrow on July 25, “Perfecting Your Call for Code Submission,” with CTO Daniel Krook.