Debug-It

Reflection

Today in computer apps we debugged some programs on Scratch. To fix these, my partner and I looked inside the project to see what was wrong. Based on the program and what the goal of the program was, we added a few things to make the program work. Looking at what is there first is a good way to fix it. Just reading what the person needs help with isn't enough. You should first study the presented program (the one that needs fixing) then think about different ways to fix it and then fix it.

These are the projects I had to fix:

Debug-It 1.1: <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/22923909/?autostart=false" frameborder="0" allowfullscreen></iframe>

Debug-It 1.2: <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/22924029/?autostart=false" frameborder="0" allowfullscreen></iframe>

Debug-It 1.3: <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/22924146/?autostart=false" frameborder="0" allowfullscreen></iframe>

Debug-It 1.4: <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/22924264/?autostart=false" frameborder="0" allowfullscreen></iframe>

DEbug-It 1.5: <iframe allowtransparency="true" width="485" height="402" src="http://scratch.mit.edu/projects/embed/22924345/?autostart=false" frameborder="0" allowfullscreen></iframe>