Game and Story Programming

June 17

Period 1

Plan

• Review class rules
• Show Scratch video
• TA demo scratch program and scratch.mit.edu
• TA demo Scratch Sensor Board
• Lab

Reflections

A good first day. Some time wasted. TA#3 came with Mac but we had no DVI/VGA adapter. So moved files to borrowed Windows laptop. Then encountered problems with program to demo. Class quickly losing interest. Running out of time. Canceled the sensor board demo. Went to lab with about 20 minutes left. Kids had great time and did well.

It was good to not show the sensor board the first day, because kids weren't even familiar with Scratch yet.
 

Period 2

Plan

• Review class rules
• Show Scratch video
• Teacher demonstrate Scratch
• Lab

Reflections

Very productive. Kids attentive and happy. Gave ideas for things to have the program do. In the lab with over 25 minutes left.

June 18

Period 1

Plan

• TA demo scratch program
• How to use Moodle
• Teacher lesson on Scratch features
• TA demo Scratch Sensor Board
• Kids go to lab, or stay with TA#1 for more with sensor board
  

Reflections

I didn't bring the right DVI->VGA converter, so TA#3 coudn't do his demo. Communication failure caused TA#1 to arrive with wrong video cable for sensor board demo. We got the media guy to adapt the cable to the TV he brought, but it was awkward because the camera had to be right next to the TV. The demo was good, and the kids liked it and learned about getting input into computers. No kids elected to remain in the classroom to see more of the sensor board. Given time-consuming problems, I postponed the Moodle demo.

Period 2

Plan

Same 

Reflections

Moodle demo went fine. TA#1 gave good sensor board talk, with TA#2 operating the video camera showing the board on the TV. We pulled it off, but perhaps should rehearse such things. 

June 19

Period 1

Plan

• TA teach a scratch lesson
  
• How to use Moodle
• Lab
  

Reflections

Didn't show moodle. TA#3 is developing his presenting skills. He tried to cover a lot of material in a short time. Lab went well.

Period 2

Plan

Same, but no Moodle

Reflections

TA gave simpler lesson, which was better. Extra long lab.

June 24

Plan

• Alice demonstration
  
• Lab
  

Reflections

Alice was very popular.

I showed some funny videos (cats on a treadmill, robot throws ball for dog) for kids waiting for class to start. They were a big hit.

I continue to closely monitor the quality of the TA interactions with the kids, to help the TAs improve.

June 25

Plan

• Proximity detection lesson in Scratch and Alice
  
• Lab

Reflections

The Scratch version of the lesson was very simple, and I think they got it. The Alice version was more complicated than it needed to be. We made two optional assignments, and there are a few submissions. Need lots of lab time tomorrow.

June 26

Plan

• Let kids go to lab early, otherwise stay in classroom for questions
  
• Extended lab time
  

Reflections

Most of the kids opted to go right to the lab, and some stayed to ask questions and see a short lesson. I continually think about the balance between instruction and lab time. 

July 1

Plan

• Lesson on variables. Scratch: Cat hikes the canyon, but first must go to the ATM. Alice: Boy does wheelie until he is tired.
  
• Lab: optional assignment using a variable similar to the lecture
  

Reflections

Kids liked the examples, and I saw several ATMs in their work in the lab.  

July 2

Plan

• Have each student ask a question about Scratch or Alice
  
• Lab
  

Reflections

Kids asked good questions, which have me a chance to show some new things and review some others.

July 3

Plan

• Quick summary
• Where to go from here: A look at Python
  
• Lab: demonstrate what you've learned
  

Reflections

I talked about where Scratch and Alice fit into tho broader world of programming. I showed some of the programs we created in the Python class.