The Blog

 

When we started the Call for Code journey early this year, our ambition was simple: We hoped to rally the software developer community around a noble cause. Millions of lines of code later, here we are, wrapping up the first year of this global initiative.

The entire Call for Code team has traveled the world, quite literally, hosting events and encouraging developers to create sustainable software solutions that address natural disaster preparedness. The response we’ve seen from the community has been overwhelming. Tens of thousands of you have stepped up to answer the call. For those who have dedicated time and talent toward creating these brilliant solutions, I want to thank you.

(RELATED: Call for Code Submission Checklist)

I haven’t met a developer yet who has complained about having too much free time on their hands. That’s why the response to Call for Code has been so magical. So many of you have worked tirelessly outside of your day jobs and class schedules to build something that can potentially save lives.

One of our amazing content partners in this venture, Joma, perhaps said it best when he urged his fellow developers not to simply be a programmer, but rather a problem solver. Code, and the ability to wield it, is just a tool in our collective arsenal. It’s what we do with that tool that defines us as developers.

After all of your hard work, it’s time to submit your project. As a reminder, these are the criteria we’ll use to judge the contest:

Completeness and transferability

  • How fully has the idea been implemented? Can it achieve an impact in the field? Can it be transferred elsewhere?

Effectiveness and efficiency

  • Does the solution address a high priority area? Does it achieve its goal effectively and efficiently? Can it scale?

Design and usability

  • How good is the design, user experience, and ease of use for the solution? How quickly can it be put to use?

Creativity and innovation 

  • How unique was the approach to solving a long-standing or previously intractable problem?

The competition platform is provided by YouNoodle and managed by AngelHack (a Call for Code Program Supporter). Your team lead can click this link to create a YouNoodle account and access the Call for Code submission form.

Your team leader will require the following information to fill out the form:

  • Team name.
  • Teammate names and emails. Remember, you can only be part of one team of up to 5 members, and your team can only submit one application. Each person must have registered and therefore accepted the Participant Agreement.
  • Submission title/summary. Describe your team’s solution in 7 words or less.
  • Describe your solution in more detail. Give us a more detailed description of what you’re building, what problem you are solving, and why it matters in less than 500 words.
  • Solution roadmap. How mature is your submission and where do you intend to take it from here?
  • Link to GitHub or other source repository (You can provide an additional description and diagrams here. Hint: Review the judging criteria and rules: https://callforcode.org/challenge/.
  • A 3-minute demo video. Record a demo of your project, upload it to YouTube or Vimeo, and share the URL. If there’s a password, please remember to share it.
  • What IBM Cloud™ services did you use?

Your team won’t be able to modify information on the form after submitting, so make sure the application is complete and the team is finalized. Through YouNoodle you can also track your project’s progress through judging in October.

For more tips and best practices on using YouNoodle, watch this video from Brian Collins of AngelHack:

As you think about submitting your project, consider these 3 tips:

  • Remember, while only the the team lead needs to submit the form, all team mates must be registered independently to participate.
  • Make sure your source code repository and video pitch are readable and viewable by the judges. Make them public or include passwords for the judges.
  • Make sure to read the submission requirements carefully! For example, make sure your video is three minutes or less.

In this video, I dive a little deeper into the best practices for the content to provide in your submission:

Again, thank you for being part of this incredible movement. Together, we’ll show the world that developers have the power to save lives.