See more news stories, highlighting our winners at canCode.us/news
canCode is a nonprofit that uses teenage volunteers to teach underserved elementary schoolers the basics of computer programming through the creation of a video game or project (examples below). In this hackathon, you'll create your own Scratch project and a brief lesson plan that lays out how you would teach your game to elementary schoolers!
Click the green flag to start the Scratch project. This is a game to teach students about recycling. The goal of the game is to sort trash into different categories before time runs out! Drag the items with your mouse to play.
Congratulations to Jackson Thrasher (8th Grade from Apollo Middle) on winning first place!
Join us for our first ever hackathon! Join as an individual or part of a team of up to 3 teens. In this hackathon, you’ll be challenged to make a project in Scratch (a block-based coding environment) and an accompanying curriculum. You’ll earn 6 hours of community service if you submit a finished project link, regardless of if you win or not. Winning submissions will be used for some of our future workshops! Scroll down for more info
All participants must register, and there is a $10 registration fee (note this fee is a donation to our 501c3 nonprofit and helps us provide underserved children with free computer programming workshops). Fee waivers are available for anyone who needs - just email firstname.lastname@example.org
All participants will also receive a 1 year subscription to CODE Magazine!
Winners will receive recognition, medals, tech prizes, and canCode swag!
Teams will race to create their own scratch game! These games should be centered around the concept of a certain scratch block such as the forever loop. It is highly encouraged to create your scratch project based off of a game that is fun for others to complete. Also, these projects must be simple enough to be taught within an hour to elementary students.
But this isn’t all! In addition to creating a scratch game, teams must create a curriculum alongside it. These curriculums will create a step-by-step guide in how the game should be taught. This could include an explanation of steps, an analogy that should be used, or anything else you can think of! Photos are also encouraged for easy understanding. The overall purpose is that the function of the code should be explained, not just the order. It’s up to the team to decide how they’d want the code to be taught as long as it is in a bullet-point format.
Submissions will be turned in once the working period has finished at 4pm. This will be done with a google form in which a link to the finished game will be submitted as well as a link to the curriculum. Before submitting make sure that your games are published and that your documents have link sharing turned on!