Vocabulary: Today our word is debug! This is an action programmers take all of the time when they are writing a program for a computer to follow! Sometimes, there is an error in the code and all of a sudden your computer is not doing what you want! When this happens, we have to debug our program! This means we look at the codes we wrote and zoom in to where the error is. This sometimes takes many many tries, but programmers do not give up! Let’s take a look at my maze and practice debugging it together!

Students work to solve my maze and discuss reasoning behind code: a. Where do I start Ozo? Where do I want him to end? Ok so I know I want my program to show how my animal Ozo would behave to survive in his habitat and eat his prey. Let’s see if my program worked! Remember, if it doesn’t work, as a programmer I look for the place it went wrong to try to fix the problem! Your thinking job is, “which code is causing the error?” (Run it) b. Turn & Talk: Did my program work? If it didn’t, which color code needs to be changed? What would you change it to? (#3 didn’t work, e went straight and got stuck in a dead end. Instead, he need to go left so we need the left sequence.GBR) c. Once name error and state change, run again to see if it works. When kids get right stamp the process. I watch my program, find the color code casing the error, and change the code. d. Now let’s watch one more time now that its right. Your thinking job this time is, “What behaviors does the robo animal show to prove he is trying to survive (speeds past predator, slows to sneak up on prey)