We Love Winter

It was another snow day today which reminds me of a recent project made by a 2nd-grade class. They missed Hour of Code Week activities so their teacher asked me to do a coding project with them.

Screen Shot 2018-02-07 at 7.25.49 PM

Over the course of three 25 minute computer lab times, the 2nd graders created these winter themed projects.  They include 3-4 clickable sprites and one sprite that introduces the project and gives directions.

Screen Shot 2018-02-07 at 7.30.31 PM

This was a true first project for these students.  I introduced all the different aspects of Scratch: Stage, Sprites, Code blocks, events, etc.  We started with making the Sprites ‘clickable’ – meaning they would do something when we clicked on them.  We did a few different Sprites do different things.  There was some confusion around having the Sprite “say” hello.  The students expected to hear “hello” spoken, not written on the screen. I guess I need to be more precise when describing that action.

We did add a Sprite that plays a Sound when clicked, and one that turns, one that changes color.  And one that glides.  I decided that the glide block would work better in our interactive project than a move block that might eventually move off the stage.

Screen Shot 2018-02-07 at 8.22.06 PM

The last Sprite we added was one that would introduce the project and “say” the directions.

Screen Shot 2018-02-07 at 8.25.27 PM

I thought they did a great job on their first project.


Snow Day Cancels Showcase #9

We had a snow day on the day of our Code Club Showcase, so it was canceled.  I decided not to reschedule it.  I sent an email to all of the parents to let them know.

I included a link to all of the finished projects with this note:

Please take a moment and have your child show you his or her project.  Give it a try.  They are all very creative and represent a lot of hard work on their part.  Well done, everyone!

We had 14 great projects this term with a lot of variety.

Screen Shot 2018-01-28 at 8.27.15 PM

Drop you, Cat Sweeper, and Parkour Cat are all difficult maze-type games. Riddler, Ghost Math and Penguin Trivia ask hard questions.  In addition, there are two virtual pet projects, three chase games, two catch games, and a fighting game.


Screen Shot 2018-01-28 at 8.34.31 PM

All original artwork is tons of work.


The creator of Kung-fu Master spent a lot of time designing his Sprites with different costumes for different fight poses.  He uses different keys to control each character and has a computer-controlled character for the user to battle.  He worked independently and did an amazing job.


Screen Shot 2018-01-28 at 8.44.26 PM

Cat Sweeper, a chase, maze hybrid

I admit I was hoping to see Cat Sweeper presented so I could find out more about it. This was another independent coder who worked really hard and shows a lot of coding skill. It even has a one or two player mode. I ‘lose’ a lot every time I play it.


Screen Shot 2018-01-28 at 8.53.58 PM

Space Adventures

The creator of Space Adventures wanted to make a Try Not to Laugh project as well but instead concentrated on a fun, challenging catch game.

I found time this week during 4th-grade recess to have the Code Club members invite a school friend to join them and test out the games they all made.  It was not the same as having a showcase presentation, but their games were played and enjoyed by all.


I certainly enjoyed coaching them and watching them develop their coding skills. Well done, everyone!



Checking Up on Individual Projects

We have two weeks until our Showcase of Projects and I’ve been checking in with all of the Code Club members to see how they are doing.  There are no team or pair projects this round which I find surprising but this year’s 4th-graders are very much unique individuals.  I tried putting two students together on one project, but they just couldn’t work together.  So they each have a similar project.  This does mean that there will be a lot of projects to present at the Showcase.


Screen Shot 2018-01-07 at 2.50.43 PM

Keep away from Bendy


The character Bendy from Bendy and the Ink Machine game is featured in a couple of chase games.  How these nine-year-olds know about this horror game, beats me.  I hadn’t heard of it, but then again, I don’t like scary things.


Screen Shot 2018-01-07 at 5.09.06 PM

Virtual Pet Dragon


Most of the students are in good shape.  The two virtual pet projects just need a few tweaks. The trivia and math quiz projects seem fine.




Screen Shot 2018-01-07 at 2.47.26 PM

Answer the riddles 

The Riddler is well coded, but I think I need to show this coder how to make his own blocks for the “you answered it wrong”.  He has duplicated his code in each “else” loop. Perfect opportunity to teach code reuse or refactoring. Now I finally have a reason to show them how those dark purple blocks work.



Screen Shot 2018-01-07 at 2.49.42 PM

This code shows up in each of his “else” statements.  



The flying cat and maze games could use some more work, but now that I’ve seen the state of everyone’s code, I think we might spend some time this week talking about game testing, how important it is, how to do it well and how to fix the glitches.

Equally important as testing for bugs, is to test for fun-ness.  We want our games to be fun.  Yes, we do.

Your Name Animated

To start off the school year, I thought it would be great to have 3rd graders work on a Scratch project and I’ve been wanting to try the animated name project from Made with Code for a while now.  You can find the resource cards here. (I printed a couple of sets) Animating your name seems like a good beginner project but not one that I do in Code Club.  And who wouldn’t want to play with their name in code?

Screen Shot 2017-11-01 at 7.29.49 PM

We started off by creating a backdrop for the Stage with the drawing tools in Scratch. I didn’t want them using one from the library, but to make their own.  Then we brainstormed ways to animate the letter Sprites – bouncing, turning upside down, changing color, spinning, growing, making a sound, etc.  This got them thinking about the possibilities. Next, we started adding letter Sprites.  Each Sprite was coded to be interactive by using the “when this Sprite is clicked” event block and adding an action to it.


Screen Shot 2017-11-01 at 8.37.28 PM

Example of 2 different letters interactivity


I used the resource cards to support students who preferred directions to be written out or visual or struggled to keep up with the general pace of the class.

Each third-grade class added their own flair to the project. One teacher decided to take photos of the students with a green screen background.  The students added themselves as a Sprite to their name project and animated themselves.

Screen Shot 2017-11-01 at 8.36.46 PM

I can’t share any of the actual student works as they include both the name and photo of the students.  We are going to record a video of the project like we do with our cloud project and include it in the students’ digital portfolio.

Another third-grade was finishing up the name project so close to Halloween that we incorporated the Trick or Treat project in with the animated names.  I didn’t present this part very well.  I needed to explain the difference between adding a costume to a Sprite and adding a separate Sprite. A lot of students made this mistake and there was general confusion.

Screen Shot 2017-11-01 at 8.55.42 PM

My next task is to finish the rubric for this project (which I should be doing right now).  The students enjoyed this project but we need to wrap these up.

Scratch Alternative Presentation

In one fourth-grade class students had a US state presentation project as one of the last assignments for school this year. I received the okay from the teacher to allow a student to make his presentation using Scratch.  He was a Code Club member and I knew he had the programming skill and drive to complete all the requirements for the project using Scratch.

While the rest of the class used Google Slides, he made this great Scratch interactive project to share.  He worked hard and I was impressed with the results.Screen Shot 2017-07-02 at 1.30.49 PM

He set the project up like a Chatbot project and used broadcast to change the backdrops. He also asked questions to keep the audience engaged.

I was available to help with the coding, but he worked pretty independently.

Screen Shot 2017-07-02 at 1.47.13 PM

I would have liked to see more picture Sprites. We also discussed recording some audio for a portion of the presentation but ran out of time. He made a bibliography backdrop but it didn’t get included in the version we uploaded. Before he presented this to his class, he made some last minute changes that are saved in his account offline and not published.

He has his own Scratch account now and I know he will continue to code and create in middle school.  That makes me really proud.

Screen Shot 2017-07-02 at 1.39.38 PM

He had a rough end of the year within his classroom and with the dynamics of some of the other students so I was glad to be able to give him some flexibility with this assignment and let him do something he enjoys and show his coding skills.

I would like to think that Scratch would be an acceptable presentation format for other school projects like this.  I have been thinking along these lines for a while and now have proof that it can be done and can show teachers what the results look like.

Coding Their Own Way

The students have begun their independent projects for our showcase in May.  They are really into their projects already.  At our last meeting, I met with (most of) the teams or individuals to go over their Game Design Document (GDD).  Over time I’ve been adding things to the GDD to make it more comprehensive but it has gotten a bit unwieldy.  Students don’t always fill it all out or their ideas don’t fit in with the description. I definitely need to reflect on the GDD and figure out what should remain and what can go.

Let’s go back to basics.  Why do I have the GDD?  Is it for the students or for me?

To make a project that takes multiple weeks to complete, but has a hard deadline, you’ll need a plan.  Planning is part of the engineering design process. In this sense, the GDD is for the students.

If you are working in a team, the need for a plan is crucial.  Who will create the backdrops? Who will code the Sprites? Do we agree on the gameplay? A team definitely needs a GDD to define roles, divide the labor, and to communicate ideas.

How do you know if it is a project that can be done in 4 weeks? What parts of the game are you not sure how to code? What should you work on first?  These questions are why the GDD is for me.  I see myself as the project manager for these 10-year-olds.  I want to ensure a project isn’t too large: “There will be 5 levels and a boss level with an army attack and when you die you turn into a zombie with a special power and then….” Yikes. I want to see that team members have communicated their ideas and agreed on the design. I want to make sure each team member has a job to do.  I want to know what parts of the coding will be tricky for them so I can find some examples of code to help them.

All of the projects this time seem pretty well thought out. There are no “try not to laugh” projects.  No Makey-Makey projects either, sadly.  There are a couple of maze games, two games with gravity, one animation, one karate game, and some adventure games.

One or two of the projects aren’t very complicated and I worry that they’ll finish too early.  I shouldn’t, though.  It will be good to have a couple of more polished, well-tested games for the showcase.

Screen Shot 2017-04-23 at 5.12.45 PM

This student is going to use this as her independent project and make a “Flappy Bird” type game.

I can’t end without sharing a few screenshots of student work.  The previous week I showed the students how to use the Tips tab to get step-by-step instructions on different games.  I suggested they try the “Make It Fly” tutorial.  This was an optional project and many chose that time to work on their GDD instead.

Screen Shot 2017-04-23 at 5.13.22 PM

This shows interesting graphic editing skills and some good coding.

Screen Shot 2017-04-23 at 5.14.47 PM

Makes you smile.

Forever, Until Done

I’ve been noticing interesting uses, or misuses, of Scratch’s ‘forever’ block.  I applaud Scratch for it’s fail soft policy and understanding the desire of 10 year olds to test things, especially to their limits.


Nested forever loops will get the job done

The ‘forever’ block seems pretty self-explanatory and perhaps that means I don’t introduce it properly. My students tend to use it in 3 ways: repeating actions, for event listeners and for looping background music.


Repeating an action forever

I introduce the forever block after introducing the repeat block.  Once they know about it, there is no going back!

In many games you wait for a certain action to happen to respond to it. One way to do that is to code some ‘if statements’ and set them in a forever loop, like an event listener in other coding languages.


Listening for the win condition

Many, many students want use it for play background music for their games.


Two dance tracks in a forever loop.  Both seem to work, together.

And I think it is with the ‘play sound’ block where things gets confusing.  I am a proponent of ‘play sound until done’ in a forever loop, and the Scratch Wiki concurs, but it seems to work without the ‘until done’ if it is the only thing in the forever loop.


Even without the ‘until done’ this code plays the whole song in an infinite loop

Other things I’ve seen makes me wonder. Why did the Scratcher feel the need to use the forever block?  Was some other code interfering with their action?


What would cause the need for show in a forever loop?

Or are they just testing things to see what works and what fails.


Forever and ever and ever and ever, just in case repeating 10 to the power of 109 times isn’t enough!

Thanks Scratch for not failing them.