Here is the curriculum document. It is a work in progress and will continue to change as I use it with students and tweak it based on what I see.
Yes, there are some! Given some scaffolding, I want students to have time and incentive to play, and in so doing, develop their own algorithmic thinking. This can be at the most basic level ("If I do this, maybe this will happen.") and at more contextual levels with programming structures ("If I make the wait time shorter, then when it loops it should go faster") and math concepts ("If I repeat a 4 step sequence 6 times it should fit perfectly on the ring.").
on a blog. I and they like to see these ephemeral instances of beauty captured and preserved. The curriculum I'm developing focuses on two key assignment goals:
- Creating and playing with patterns: This provides a hook into mathematical thinking and also allows them to find a pleasing order in the devices themselves.
- Telling stories: Creating a narrative behind the colors and movement makes the devices come alive in a different way, taps different thinking and feeling areas of the students.
Decisions I've Made
Here are some decisions I've made as I've worked through and revised the curriculum:
- As mentioned before, turn off the lights!
- Put up one slide of the curriculum slide document, discuss it, work with it, then move on to the next as a class, but provide the link for those who want to explore ahead. At first, I tried keeping everyone on the same slide but found slower students were holding back others eager to move on. Then I tried giving everyone the link and said go at your own pace and it became a chaotic mess. So the happy medium seems to be provide structure and instructions for most while letting a few who really get it explore ahead.
- Attach the 3d printed shields to the Arduinos with rubber bands and, though it's hard to do, solder the pins to the holes in the NeoPixel ring. Any slight jostling can cause pins to lose contact which makes the board reset or flash randomly or go dark, which is unsettling to students.
- I put the slide on moving off the command line to write programs in a separate document much earlier than it had originally been. I didn't start right off with that because I wanted them to see they can get some nice things done on one single line of code, but will eventually need to break it up into separate lines to make it easier to see what they are doing. Initially I thought they could get all the way to the activities on randomness, but they got really bogged down as soon as they started using repeat, especially missing omitted parameters. So I moved it up to right after repeat so they could experience that problem and then learn that whitespace is a necessity for program clarity.
- Also regarding the above note, I found that they really quickly wanted to be able to make programs that animate, so they needed the loop command to do that easily almost as soon as they had learned to work with repeat.
- Tip: If working on a Mac, TextEdit must be set in the preferences to plain text mode by default rather than rich text formatting mode.
This document is a real work in progress! At this time I haven't even worked with students past the One-At-A-Time slide, so I'm sure this original will still change.