Scratching My Way

This week in EDTECH 597, we were tasked with modifying two of the assignments found at the end of chapters 2 and 3 in a way that not only showcased the ability to solve the problem presented but also demonstrated that we are able to manipulate the code to do as we wish (see below for my completed projects).

As I continue to get more comfortable with Scratch, I am noticing that I am getting better at:

• Figuring out how to get the program to do what I want
• Spotting errors within my code
• Navigating between multiple sprites and code.

Of these skills the one that is most intriguing is spotting errors.  In EDTECH 502 we were tasked with creating webpages.  While correcting errors could prove difficult, spotting them was relatively easy (typically the numbers for the lines would appear red).  However, Scratch does not have that, so the ability to spot and correct errors quickly and easily becomes a very important skill.  I would also suggest testing the code repeatedly throughout the creation process to make spotting those errors easier.

As I work as a tech integrator, I am starting to see a variety of different possible ways this program could be used in Art, Math, and Language classes to provide activities that could challenge some of my learners.