Kinder
Kinder Workshop
Teaching coding is no easy feat, and you’ve done an exceptional job at it this school year! This workshop is designed to help you continue building your confidence with the 9 Dots curriculum during the second half of the year. We’ll begin by reviewing key coding concepts in your grade level’s curriculum, followed by dedicated planning time to ensure you are well-prepared to lead your upcoming coding lessons. Finally, we’ll provide a sneak peek of what’s to come in Module 4 at the end of the year.
Quick Navigation
Review Coding Concepts
Module A introduces students to the world of coding in an online coding environment we call PixelBots. In Modules A1 and A2, students learn about the different parts of a computer and the fundamental concept of sequencing, or writing code in a specific order to give a computer directions. In Modules A3 and A4, students continue to write longer sequences of code while being introduced to two new kinds of coding challenges: reading and debugging. Let’s explore the three types of challenges below:
1) Writing Challenges
In PixelBots writing challenges, students write code using code blocks to match their grid with the goal grid displayed in the upper left-hand corner.
For a deeper look into sequencing and writing code, watch the video below:
Try solving a Writing Challenge below!
2) Reading Challenges
Reading challenges show students how computers interpret code. In a reading challenge, you’ll find a sequence of code that is presented on the right-hand side of the screen. Your task is to read each block and then replicate its action by pressing the corresponding button located in the control panel on the left-hand side, just below the PixelBot grid.
For a deeper look into reading code, watch the video below!
Try solving a reading challenge below!
3) Debugging Challenges
Debugging challenges teach students how to find and fix errors in code that is already written. In these kinds of challenges, students are presented with pre-written, error-filled code, and they must find and fix those errors, or bugs1. You can only make as many changes as the change limit allows for each respective challenge. If you make too many changes, click ‘Reset’ and try again!
For a deeper look into debugging code, watch the video below:
Try solving a Debugging Challenge below!
💡 Think about which challenge type(s) could be challenging for your students. What are some ways you can support them?
Review Lessons & Create Your Action Plan
Prepare for your upcoming lessons by reviewing lesson materials and creating an Action Plan. Start by reviewing the lesson plan, slideshow, and challenges, and then decide which section(s) of the lesson you’ll lead or co-lead with your coordinator.
💡 Use the Graphic Organizer for step by step instructions to create your Action Plan
Preview Module 4: Bug Squashers
With any remaining time you have, take a sneak peek at what your students are building up to!
The Kinder curriculum includes a 4th module, Module A4, which has students continue their study of debugging. It begins with a lesson that introduces arguments, numbers or colors that change what code does, through writing challenges. Then, they learn how to debug code by changing number arguments. The lessons following cover different debugging strategies such as removing code and adding code to resolve a bug. This module includes two review lessons and a culminating Level Up Challenge, which we encourage students to complete independently.
You can take a deeper look at this module by reviewing the Scope and Sequence here, or via the 9 Dots platform.
Survey
Thank you for attending our Semester II PD! We take teacher feedback seriously, please take our survey here.
Access Resources
For more practice, please log onto the 9 Dots platform to review lesson resources. If you need some support navigating our platform, please review the 9 Dots Teacher Guide.
If you would like some additional one-on-one support, please email your school’s Impact Manager or email us at [email protected]
Footnotes
[1] A bug is an error that prevents our code from behaving the way we want or expect it to. Why are these errors called bugs? You can click here to read about the first computer bug!