TAP Lab Visit

Last night I went to the Te Atatu Penisula Community Center where they have an awesome makerspace to learn about Arduino. I heard about this through meetup. The idea was that anyone interested in Arduino could get a crash course in the basics, even if they didn't know anything about it.

Some of this may be too technical for some, but keep on reading for my thoughts on makerspaces in general.

I figured that since I want to get students making robots (at some point), I'd better learn myself. There were a good number of people there and I was given help in a small group of 4 people. We were taught how to just use the Arduino to light up an LED using both parallel and series circuits. Then we got the chance to experiment with coding some LEDs to blink and to fade. While not completely earth shattering stuff, it was a good first step with not only the physical setup of the Arduino and breadboards, but also with the coding for Arduino.

As I have been slowly sharing with people, one of the things I'm attempting to do at the moment is to actually organize the maker educators in New Zealand, so this visit was also a good way of networking with other people, outside of schools, who have knowledge. In an long discussion with some of the regulars afterwards I was able to get a good idea of what is out there in New Zealand at the moment (a growing number of makerspaces for adults, along with a network connecting them - but still a lack of organized network for school, something which I'm prepared to start - Maker Ed NZ, which is quickly or slowly becoming my pet project).

I'll be writing more about makerspaces and why I think they are important and necessary in schools later, but I did want to share what I did and what I learned. Here's a short video of the LED lights I was able to get to blink in an alternating manner.

CS4PS (Or My First Trip to the South Island)

I recently made the trip down to Christchurch (which incidentally was my first time on the South Island after living in New Zealand for 4+ years) for a Computer Science for Primary School course put on by some amazing educators from the University of Canterbury.

A major focus of the course was using Scratch to code. We talked about learning both coding and about using coding to teach other subjects. The things I learned in two days absolutely have blown my mind with respect to coding in the classroom, as well as the possible uses of Scratch.

We started off the two-day event by discussing (and completing) several unplugged activities to teach computational thinking (because that's what coding is about, NOT the computers). We learned about binary and how to represent numbers with only ones and zeroes. We did a massive activity which pretty much led us to writing codes with musical notes. We also discussed ways in which computers verify data (through ideas such as parity - see the Error Correction activity in the below link) and how data can be transferred through the Internet securely (hint: it travels through the web three times, instead of once). A lot of these activities can be found on http://csunplugged.org/.

Then came the chance to actually get programming with Scratch. Up until now, I've always looked at Scratch as a way to 1) make games and 2) tell stories. Though I have had some coding experience (FORTRAN in my first year of University, some JavaScript course on Khan Academy and lots of HTML coding), I never put 1 and 1 together. Well, I finally figured out what the 2 is. The following are some programs I made for activities we did this week as well as some programs that I might use in the near future (i.e. next week when I go back to class). Some of these came from direct problems - i.e. can you make a program that takes such and such info and tells you this and that result. Some of the challenges involved using only a small number of blocks. The programs are down in the order I made them, so you can see the evolution of what I've learned (keep in mind, this was over two days!).

Debugging is also an important skill that we discussed. The idea here is that no code will be perfect when first written, so we need to be able to go through our code in various ways to check that it does what we want it to do. There are many different ways to check. When using variables you can show them or you can have them said at certain parts of the way. All cases should be tested for to see if all cases work (boundary cases are specifically important). We got to do a quiz on this and I ended up winning some parity magnets for the efforts of my team.

These ideas will likely be the basis of the upcoming digital technologies curriculum in New Zealand, so this is a great way to get started. Computer Science doesn't need to be an add-on to our current curriculum, it can fit in nicely with everything we are already doing.

A side note: This was apparently the first Google-sponsored CS4PS in the world! It's definitely a great idea and should be repeated over and over for as many teachers as possible.