Name: 

Step 1.
List five situations during the past week when you used instructions written by someone else.


Step 2.
What are instructions good for, in general? Why do we write instructions? What purposes do they serve?


Step 3. 
What was easy/difficult about being the bossy person?


What was easy/difficult about being the bossed person?


How does this activity relate to what we're doing with Scratch?


Step 4.
What is the difference between a sprite and a sprite's costume?


When might you want to add a new sprite instead of a costume?


Step 5.
While creating your sprite in step 4, how many blocks did you add before testing them out?


In practice, how often should you stop "programming" and see how it works?


Step 6.
How can you test small portions of your code after it gets relatively long or complex?


We will pause the lab at 30 minutes and 60 minutes for a gallery walk of the projects-in-progress. We encourage you to look at each others' code and ask questions about unfamiliar constructs.


Step 7.
Which aspects of the programming process apply to Scratch? Which ones don't?


How does your Scratch project relate to object-oriented programming?