A Day Full of Lego

Anyone who knows me (or who has been in my home) knows I have a little bit of an obsession with Lego. So when the opportunity came up to learn about some Lego resources that can be used in the classroom, one could easily imagine that I would literally jump at the opportunity. This morning I made the drive down to Te Matauranga School and was immediately transported back to my childhood dreams when I saw the sheer volume of Lego that was present at the school. It was amazing!

And it only got better from there. We spent most of the day working on some hands on activities, all to do with Lego WeDO 2.0 as well as with EV3 robots. Our amazing facilitators (who came across the ditch from Australia) made sure we had a lot of things to do.

The first thing we played with, was the WeDo 2.0. I had seen this in previous years (I'm sure if you go back in my twitter feed, you'll see it) and in the interim had never really gotten a chance to learn more. We did a few activities with this. The first was to take 10 pieces from the set and make any animal. We had two minutes to do this (with the wonderful advice of start with your hands and let your brain catch up) and as you can see in the picture below, not one of us made the same as another. It's a great way to get started when you're working with Lego (or anything else for that matter) to show that everyone has great ideas and they can be very different from each other.

We then used the app to make a windmill (or a fan) and then have a bit of a play with the coding. It is very easy to use, and has a lot of different functions. Our last challenge was to make a music machine. I spent a good bit of time of this, iterating and making new versions, adding features as I got inspiration. It was all good fun.  Here's a tweet & video of what I made with my partner:

Building a sound machine. Gotta love having a full day of playing with @LEGO_Education looking forward to making some more cool things! #MakerEdNZ #lego pic.twitter.com/TuSSQZLLjw

— Michael Davidson (@michaelteacher) August 26, 2018

After a break for morning tea, we spent the remainder of the day with the EV3 robots. While the WeDo is for younger children, the EV3 has more capabilities and is more suited for older learners. We first learned how to make a quick build (not Lego Certified) to do some testing on getting the robot to move an exact distance. We started with 15cm, then 40cm and finally we tested our calculations on 2m exactly. We did this, however, with a minifigure called Daredevil Dan. Due to some inaccuracies at the 40cm level, our calculations were out quite a bit. Though eventually we managed to get it close (though, I guess it didn't work if we just nicked him at the end). Our trials are reversed here:

Daredevil Dan almost made it (maybe he should have taken a step back) #lego @LEGO_Education pic.twitter.com/xePFKZJFbE

— Michael Davidson (@michaelteacher) August 27, 2018

This is not Daredevil Dan's day... #lego @LEGO_Education pic.twitter.com/epnWCZtFS7

— Michael Davidson (@michaelteacher) August 27, 2018

The last challenge of the day was to make a robot that moved WITHOUT wheels. Again, I spent a good amount of time iterating and improving our robot. On carpet, our robot moved quite quickly, but on the lino, it was not so fast. It was still quite menacing and I think I may have a future in some sort of robot wars type competition.

Silly walk challenge. @LEGO_Education #LEGO pic.twitter.com/zp55cGvtCh

— Michael Davidson (@michaelteacher) August 27, 2018

Another thing that we discussed was the First Lego League. Every year Lego sets out challenges for both Juniors (using WeDo) and Seniors (using EV3). You can register, get a pack of pieces and then join local competitions which can lead on to national and international competitions. Lego First New Zealand seems to be growing rather quickly, so it's probably a good time for schools to get in on it. The national competition here is on December 1st, I believe. All you need is an EV3 or WeDo and to sign up on the site to get the materials (which do have a cost, but it's worth it, I'd say). Even though I can't do it this year (my school has no learners until next year) it's definitely something I'll be looking into for next year.

Official Launch of The Monthly Maker

It is with great pleasure and after lots of last minute scrambling that I'm able to announce the release the first issue of The Monthly Maker. Due to an issue with gmail, I've moved distribution over to Google Groups for some subscribers today. Everyone should have received an email so if you didn't please check your spam or junk folders. There may be some emails in the coming days to add the remainder of the emails to the group for distribution. Apologies while I sort out the technical details (though admittedly the timing was great as I was able to get help from an actual Googler!)

You can access the newsletter below by clicking HERE.

Anyone who would like to receive future issues, you can subscribe HERE.

Feedback is always welcome.

Enjoy!

Book Review: Code in Every Class

When I went to Sydney last year for the Innovator Academy, we were all given books. I was lucky enough to be given a book that related exactly to my project: Code in Every Class by Kevin Brookhouser and Ria Megnin. I only recently got around to reading it, which is unfortunate for me, as it has proven quite useful when it comes to wrapping my head around certain things.

The book aims to be a help to all educators, regardless of their skill level when it comes to coding and computational thinking. A beginning will take away a lot from it, but so, too, will an educator experienced in teaching these concepts.

The bulk of the first few chapters deals with the rationale behind teaching coding in class and how teaching coding to everyone is something that we must pursue - even if those learners will never code another line in their lives. The arguments and ideas set forth are extremely helpful in persuading those who would put barriers in front of those of us who want to teach coding.

The authors explain how coding can and should be integrated across the curriculum (hey, doesn't that sound familiar - at least I know I'm on the right track) and it gives a lot of foundation information that will help any beginning get a foothold. And what they don't give (or don't have time and space to give) can be found in the many links shared throughout the book.

The last section of the book has a large number of activities that can be done, ranging from beginning lessons to quite complicated ones. Again, there are many links shared so that the reader can get more information.

I would definitely recommend this book to any and all educators, even if you already are using coding (or more accurately, computational thinking) in your practice. It will help you spread the word and more likely than not, give you many ideas to begin or transform the way you teach coding in your classroom or with your learners.

It can be found on Book Depository and Amazon.

Coding Across the Curriculum: Update 2

It's been a while since I've been able to update any progress on my Innovator Project, due to several events beyond my control, but over the last few weeks, I've been able to renew my focus on these parts of my life and make some fairly significant progress.

I think the timing of this can be quite helpful, because I know several NZ schools have not really been able to implement the new Digital Technologies Curriculum. The goal of this project is help educators implement computational thinking into their program, so there's no judgement here, just resources and assistance.

New Videos
I've managed to finish my third video for Coding Across the Curriculum and then start and complete the fourth. I've included the two here for anyone and everyone to try out themselves or with their learners. The first is focussed on making stories with Scratch and the second will help you learn how to make calculations - both simple and complex - using Scratch.

The actual process of making the videos is becoming easier with each time - though I'm still pretty nervous when filming and often trip over words - sorry about that.

Using the Videos

I've been able to do some real world testing with several of the videos I've made. With my Habitat of 89 learners, we've worked in pairs to make a quiz each. The children had a lot of fun doing this and were, for the most part, able to follow along with that video on their own. Several of the children added their own extras to the work they were doing, which was a nice added bonus. We were able to have some good conversations about coding - which was really the whole goal of the process. I even saw some children use a quiz in Scratch for their iExplore (basically Genius Hour) project. It was nice to see that in action. I did find that the Choose Your Own Adventure video was a bit harder for the children (aged 7-9) to understand, but many of them did get it.

So my recommendation to anyone out there: just give the videos to your students. Let them have a go. If you don't know how to code, do it alongside them. Start the conversation. It's not about being expert coders, but it is about being creative and solving real-world problems and learning how to think logically.

Or, as an educator, you could watch the videos and learn how to do the coding projects on your own and then teach them the way you want. They are meant to help you and help your learners develop this skill and way of thinking.

Where to Next

I'm not sure how many people will make it this far into the post, but I do have a few exciting things in the pipeline.

First off, there are more concrete plans for future videos. The next video will show how to make an interactive display (much like you would find in a museum) and future videos will deal with art, music, VR, spreadsheets and more. Now that I've found a rhythm in making these, the plan will be to have a new one every few weeks. At least that's the plan.

There are two more next steps that I am in various stages of implementing and a third one that will possibly be a bit further off.

The first new thing that I'd like to announce officially here (and announcements on Twitter and Facebook will follow in the coming days) is that there will be a MakerEdNZ newsletter. The current plan is to have a monthly, one page newsletter that will have links to various resources or videos. There will be a coding tie-in, which will highlight a specific coding block or command (and linked into a video which uses the same block or command), a link to a Digital Breakout and some links to ideas that can be used in the classroom. If you are interested in subscribing to this newsletter, please fill out the subscription form below. I expect the first issue to be ready to be emailed out in mid-April.

The second thing I'm starting to explore will be a coding contest. I'm likely to make this NZ-wide. I've still got to work out MANY details of this, but it is definitely in the pipeline and I would like to do this before the end of 2018. 

The third thing I'm looking at doing is to start some free meet-ups for educators who are interested in discussing or learning about coding. I want to focus on the other things at the moment, but am definitely open to anyone who is willing to help me run these. But this may be something that comes about in 2019. We shall see.

So that's where things stand at the moment. I'm pretty excited about all the ideas I've been getting the last little while and the fact that now I've got a resource of four videos (over an hour of content).

Have a look at the videos, and if you have feedback it will be greatly appreciated. If you like the videos, subscribe to the channel and use them with your learners. The support will help and it lets me know that they are being used.

Look forward to some new updates in the coming months and in the meantime SUBSCRIBE to the upcoming newsletter.

Fourth Time's a Charm, or I'm a Google Certified Innovator

Three times before I have applied for the Google Innovator Academy and three times I have received the rejection email with varying degrees of dismay. But each time I refused to give up, knowing that if I kept at it, I would be selected. That being said, I was still quite nervous for this current round, since it was in my part of the world.

I was not to be dismayed this time. While on vacation in New York City, I had a flurry of activity on my phone, which all indicated that I had been accepted. I was extremely busy at the time so it took a while for everything to sink it. After my holiday, I came back to a very busy school term, so was also quite rushed for time.  That being said, I still managed to get everything done in time for the academy, which was probably one of the best experiences I've ever had.

If I had to choose what my favourite part of the two and a half days, I'd have a real problem. Pretty much all of it was incredible. The best I can do is point out two aspects of the academy that will likely be instrumental in going forward: The connections with other innovative educators around the globe and the design thinking process.

With me at the academy were 36 other educators, and many coaches and other EdTech experts. My close team, the Lucky Unkos made immediate and strong bonds with each other, and functioned not only as a well-oiled machine in all the activities we did, but also ended up winning quite a few things (or coming close seconds). By going through the process together, we formed something of a family group together and will now have each other to lean on through difficult times. One of my good online (and in person) colleagues was actually placed in this group, so it was nice to have that, but it was also nice to work closely with others in this capacity.

The whole point of the academy was to help each of us work on an identified problem in education and to develop a solution to it through the design process. Though I had had some experience with this, clearly I didn't know enough, because over the 2 and a half days I was immersed into the world of design thinking in a way that I could never have imagined. We started from the beginning by looking at all of the reasons why the problem exists and then examining the person (or people) to whom our solution is directed at. We spent lots of time slowly developing our ideas and giving each other feedback. Eventually we all developed a prototype of what our solution will be.

This process was absolutely amazing and I've already brought in many of the ideas into my practice. In our iExplore block, I've taken four of my groups and run through a watered down (but still pretty robust) version of this with the projects they had been working on.  Already the results have been pretty positive with all four groups working on some pretty interesting solutions (so watch this space in the coming weeks when I'll have time to share what they did in more depth).

My actual project is based on helping educators integrate coding into the curriculum. Here in New Zealand, computational thinking is meant to be part of the curriculum next year. Before the academy I did a survey and found that many educators were not teaching it (about 50%) and those that were had had very little training or support. So I wanted to change that. After the whole process at the academy, I decided on making a storyboard of a video for my prototype. I'm currently in the process of turning that storyboard into a script which will then be filmed. It has been a busy few weeks since I came back (mostly taken up with ERO and some big personal things), so I'm hopefully going to find some time in the coming week to work on it. At any rate, I was matched with my mentor today, so that's another great step in this whole process. I look forward to sharing with everyone how this project is going in the future!

ISTE (Round 3)

So once again I made the trip across the Pacific to the US of A to ISTE. After the first time over, it was hard not to make the trek again. There simply is nothing like it (at least that I've been to) over on this side of the world. This year, I felt like a veteran, knowing the best way to get the most for my time in San Antonio. I wanted to avoid wasting time listening to people talk at me and make some real connections with real people doing amazing things. I also had a long list of ISTE friends to reconnect with. A lot of people go to conferences to hear the latest new thing (and I definitely like learning about that stuff), but connections are more valuable to me, with some really innovative, off the wall ideas thrown in there.

There were some clear themes throughout the conference this year.  The most obvious thing that (it seems) everyone is doing is VR. So many different presentations and poster sessions included it. In particular, I did visit the CoSpaces booth and was quite impressed with the ability to create your own 3D environments. I'll definitely be watching their website for the educator and school accounts (I could be a bit off on the names, though). There's also some really cool new AR stuff coming from Google

I also had a lot of good conversations and got some good ideas from a lot of the big robotics companies: SpheroEdu, Wonder Workshop, Ozobots and a few others. They all have some pretty helpful STEAM activities and other lesson plan ideas that can be used. 

The same goes for some other companies that produce other technology things: OSMO, Little Bits and Bloxels stood out, as well as Microduino. There was a company that made some neat little robots called SAM robots, though I can't seem to find a website or pictures of those. As always, a visit to the Lego Education booth was one of the highlights (if I had a million dollars, I'd get two of everything!)

Though it was not as prevalent as years past, there were still lots of ideas for using Makey Makeys, both with the good people at the booth and with presenters. I did learn that you can have an output (eg, make a light flash), so that was kind of cool. Plus seeing what some learners have done with it was helpful to see how it could be used.

All of the above are definitely on my wishlist and would be super helpful in creating a fun and STEAMy classroom that engages my learners. Over the next few weeks/months, I'm going to look at how I can use what I've got to do these things, but also at ways of obtaining some more of these things.

But by far the most important thing from ISTE, as I mentioned above, was the people. Last year I met Shannon while we were each making our own binary bracelets on the first day. We then ran into each other multiple times over the course of the conference. Last year we said we would collaborate on something, but then never did. This year, if you can believe it, we ran into each other once again on the first day, and once again making binary bracelets (why both of us needed another one this year, I'm not sure). We caught up briefly and visited each others' presentations. Now, we've been talking about doing some sort of global collaboration project with each other this year and co-presenting at ISTE next year. So that's kind of cool. And hopefully putting it up here will also help me not forget to do it this year!

I've also made another handful of contacts of educators in the US who want penpals (have actually made contact with one, and planning on one or two more right after this blog post).  Furthermore, saw my friends from Kiva again and will be wanting to perhaps get some more things going on with them.

One of the big things that has come up in EdTech in recent years is the idea of ambassadors for certain companies. I'm definitely looking into a few as many companies do not have educators from New Zealand working with them that closely yet. Hopefully within the next few months I'll be on here writing about all the new connections I have (as well as my global collaborations).

To anyone who has never been to ISTE, my advice to you is GO! Chicago next year is a wonderful city and ISTE is an amazing experience. The incredibly inventive things you'll see and the inspiring people you'll meet (and in turn inspire yourself) is definitely worth the cost of getting there (and as an added bonus for NZ educators, you get a week of summer in the middle of winter). If you're interested in coming along next year, let me know and we can meet there! The site for Chicago is here. Calls for presenters open in less than a month!

A Little Bit of Cross Campus Collaboration

Over the last few weeks, I have been privileged to have the opportunity to do some collaborative learning with our local Secondary School - Ormiston Senior College (OSC). One of the teachers there, Mr Chandar K, has been using the Sphero robot in his teaching and had heard that we were using them as well in the primary school. He contacted us and offered to take a small group of our learners and do some activities with them, to teach them how to code the Sphero Robots.

I've had a couple of Spheros (and two Ollies) and have been letting our learners use these all year, but I wanted to learn how I could use these a bit more. We were a bit limited by our small numbers, so the opportunity to use 8-10 of them in another setting was very enticing. We asked the 90 learners in our habitat which were interested and got 18 who were keen to make the once weekly trek through the Junior College to go learn about how to code a robot.

For the past month or so, we've been learning and developing our coding capabilities and I've been getting lots of ideas as to how you can manage a robotics curriculum in a school.

On the teaching side of things, Mr Chandar K started by letting the learners free drive with the sphero. This was the last time he let them do this. We had a couple of races to get them used to how the sphero moves and what it is capable of doing.

From there we did some simple coding - making the Sphero roll for a short amount of time, at a specific speed in a specific direction.

That was the end of week one. When we came back the next week, we tried another challenge: to make the robots go in a square (and then back again). This proved difficult for some learners as they had to change the directions (so we learned a bit about angles), and adjust the speed or time so that the sphero would go the correct distance. Some were able to complete the task AND make the robot retrace its steps.

The third session involved our learners trying to program the sphero around three objects inside a square - so essentially they had to program a triangle. This was also difficult, but many managed to do it.

Our most recent session involved the learners coding the sphero to go in an L Shape on the carpet. We had some difficulties today and discussed concepts like friction (the carpet was pretty bumpy itself, but the little markers used for the shape were slowing the sphero down a bit and knocking it off course) and fractions, ratios & proportions (when trying to adjust the distance the sphero would go). As a learning coach, I am starting to see a lot of the mathematical applications with using a sphero.

As you can also find out in the video, we learned about putting a delay between roll blocks so that the sphero goes in straight lines, instead of curved.

So why was this helpful? Well, just on the surface this was great for my learners because they got to experience these robots and learn in ways that we cannot yet provide (with only my two personal sphero at our school) and I was given a great starting point for what I can do with them and lots of ideas as to where we can take this.  But there are deeper implications from this experience. At Ormiston (and I mean the three schools combined) we have a great opportunity for some great collaboration between all people (leadership, learning coaches and learners) and this was a great example of what could be done. I know Mr Chandar K is also working with the Junior College. This will hopefully provide future opportunities for the adults at the three schools to sit down and figure out what we want to teach when it comes to robotics and to start to share knowledge and resources.

As for next steps in the coding, I'd like to start introducing some looping functions and then eventually if statements. There is a lot that can be explored in this coding and the doors are starting to get a bit wider for me.

If anyone out there has any other innovative ways to use these robots, please share in the comments!

Exploring Literacy and Coding

A while ago, I participated in a wonderful Twitter chat with #digitaledchat where we discussed what you could do with robots in class, such as Sphero. One of the things that came up was using them to create stories or videos by coding the robots as characters. I liked that idea so much, it got me to thinking quite a bit about how coding and literacy could be combined.

I've tried really hard to make my class a creative one, in which my learners are able to explore different ways of learning that are fun, creative and exciting. I want the children in my charge to wake up in the morning, excited to come to school and do their work (which they won't see as work). I have had many different ways of making stories and being creative (including Stop Motion and Digital Storybooks) so it wasn't a big step to try some new things. Here are three ways in which my learners used coding or computational thinking to create stories:

Choose Your Own Adventure Stories Using Google Forms

Many of us have read these books as children and this idea is definitely not a new one. You can use the "go to page based on answer" feature of multiple choice questions to direct readers to new pages based on their choices. When we first did this, I used Google Drawings to plan out the story (it can get very complicated if you have a lot of choices) but it isn't always necessary. A pair of my learners created this story earlier this year.

There are other ways of making stories like this, including Scratch.

Stories on Scratch

This idea came from CS-First.com where you can find a whole 8 lesson module on coding stories for code clubs, though if anyone has used Scratch Jr, that's basically what that app is for. The idea is simple: code the sprites to speak to each other and interact. As coding knowledge increases, so too does the complexity of the stories. This is definitely an area to explore for reluctant writers who happen to like coding (and I've noticed the majority of my learners are liking coding more and more everyday, some even attempting to code a Choose Your Own Adventure story).

Coding Robots to Tell a Story

This was the big idea from #digitaledchat that I have been waiting a while to try. We only have made one attempt at this, but it went, in my opinion really well. Some interested children joined me for a short brainstorming session. We came up with some characters and starting thinking about what their story was going to be about. Some other learners got interested and joined us at this point and the discussion started taking off. I backed off and let them sort things out. There were varying levels of coding abilities in the group and they were able to support each other. A lot of the story didn't really utilize coding knowledge, but it was a fantastic start. Again though, a little disappointed that these children won't get to try this again with me, but I'll keep on introducing these ideas to children and see how they develop.

The plan with this topic is to continue to explore it further, get children making more and more stories using their coding skills and then to share this in more depth next year (hopefully at GAFE & ISTE). So keep an eye out if you're interested as I think this is an exciting way to develop a plethora of skills amongst learners.

My Learners Are Amazing!

Every term, each team at my school has an assembly where the learners come up and share something they've done. Each term, I've been the "lazy teacher" and had my learners come up with what to share, prepare everything and then present, with very little input from me. The first two times have been pretty good, especially considering they've likely not had any guidance in doing something like this before.

This term, after going to CS4PS, I went pretty hard out with teaching coding and computer science. I have some students who have really enjoyed doing coding (through code clubs and some of the lessons I've done in class) and they decided to share some stuff they've done on Scratch. The group chose itself, and was inclusive of all learners who wanted to participate. For few days of their preparation, I did absolutely nothing, except remind them they had a deadline. They worked together, having arguments and discussions. Tears  were cried, but followed by talks to fix the tears (I may have nudged them to have those talks).

We had a practice on Friday morning and afterwards in class, we had a little critique to help them along. We first talked about all the great things they did (and there were a lot!) but then we discussed how we could improve. It was amazing to see how supportive and positive the rest of the class was in helping them along. They realized most of what we said anyways, so they were also being self critical (which, is yet another thing I want my learners to be).

Then this happened in the afternoon:

I'm so proud of them and I didn't even do anything, other than guide them along. This is all their doing. It's been a fun last couple of days in class with this and some other amazing things going on (hopefully I'll be blogging about another group that did another AMAZING thing this week, but we have to finalize some things on Monday).

TAP Lab Visit #3

This Wednesday I returned to the TAP Lab to continue my education in all things Maker. Most of this involves Arduino and other types of coding, but we'll see where things take me and how much time I'll actually have in the future to come back (it is pretty far away - but definitely worth it).

Today's session started with me figuring out another sensor - a temperature sensor which is surprisingly accurate. Then the very helpful people at the lab started telling me all about all the parts I had in my Arduino kit, including some displays. Well, I was intrigued. My big thought was to get the display to show the temperature. Well, it was a massive job just to 1) figure out how to hook up the display to the Arduino board and then 2) figuring out the coding, which had a very simple, but inexplicable error.

The code we found on the Internet for the lights was giving some really strange results. We poured through it, trying to figure out what went wrong. Then we started testing things to see what changed. It became apparent, at one point, that the lights were doing the opposite of what they were meant to do in the code. So, I changed all the 'trues' (which the code said meant the lights would go off) to 'falses' and amazingly, the display lit up as it should have. It was a good lesson in debugging, though it got pretty frustrating at one point, and I was definitely in the dip (growth mindset FTW!). But this only led to a static display. I managed to change the display to my birth year and then discussed ways in which I could program the numbers to change - though due to the tediousness of the code I'd have to write, I put that off for another day.

Learned how to code a 4digit display today at @TAPLabMakers Next step: make numbers change! #MakerEdNZ #hacksterlive pic.twitter.com/KkrINLhHb2

— Michael Davidson (@michaelteacher) August 31, 2016

Since I remembered to bring my mBot to the lab, I decided to have some fun with its display as well. It is much easier to program the lights there (it's all visual, and you just need to click on the squares), so I was able to spell out all the number words to ten and get it to count up. I bet I can modify this program to make it do addition or subtraction (or many other things). Hmmmmm.... I do love how learning one skill can get you thinking about how it can be applied. Have a look at the video of the lights changing.

Today was a fantastic lesson in what actually goes on in a makerspace. It was often quiet when I was working, but when I had a problem, many people there were willing and even eager to help me. That's the kind of atmosphere I'd like to create for makerspaces. I spent two hours there, but it felt like 10 minutes. Again, that's what I want for MakerEdNZ. 

TAP Lab Visit #2

Once again, this past Wednesday I made my out to Te Atatu Peninsula Makerspace for their weekly meetup. I wanted to a) learn more about using Arduino (specifically sensors), b) potentially figure out what's wrong with my mBot and c) continue to build a relationship with people who actual know how to run and organize a makerspace so that I have some real-world experts to help with MakerEdNZ.

Overall it was a pretty good evening. Though the weather was bad there were a good number of people who could help me figure some things out. It was nice being in a room of problem solvers - people who will try different things to figure stuff out. With some help I set up a photoresistor sensor on the Arduino board to check for light. We had a good discussion on what the results actually meant (I was getting high numbers when it was dark and low numbers when it was light, which was confusing to me).

The subject of my non-working mBot came up as well. Another person there helped me use their mBot to try connecting it via the 2.4GHZ connection. It worked reasonably well and I was able to explore a little bit about the sensors on the mBot. It was good because while I was doing so, I was able to imagine in my head how these lessons and ideas could be put to use in a classroom or makerspace (and now I have some skills to work with as well).  The unfortunate part was that when I went to school the next day, I was unable to get the mBot working completely, so there must be some other issue. So there will be a visit #3 coming up soon (I've signed up to go next week and the week after, but we'll see if I can actually make those days). 

Anyone interested in makerspaces or joining us for #MakerEdNZ, I'd suggest visiting a community makerspace and see what they do. Everyone I've met has been very friendly and extremely willing to help. You can find lots of those on Meetup.

ISTE 2016!

It has taken me a few weeks (almost a month, in fact) to fully come to grips with my ISTE 2016 experience. To sum it up in word: Amazing! But obviously there were some really good takeaways that came from the experience. I'll try my best to share all of what I learned, but no doubt some good stuff will get left out.

edit: Now it's almost two whole months after ISTE! But still thinking lots about it. Some of this may be repetitive because of the time between when I started writing and when I finished, but I think the tone that will likely be consistent throughout will convince you of the value this experience had for me and could have for you in the future.

People, People, People

The first place you need to start when dealing with ISTE is the people. I'm not talking about the sheer number (though that is staggering on its own). What I'm talking about is the people you meet. The biggest draw for something like ISTE is to meet lots and lots of like-minded and incredible people. And don't get me wrong, EVERYONE at ISTE is incredible. When I told one of the people I met that "I'm just a classroom teacher," she responded by saying that nobody is "Just" anything. We all have something to offer, no matter the title or experience. Though I did realize this before, it was interesting to see how our language can affect our perceptions (and the perceptions we create in others). Later on that day, I met someone who said pretty much the same thing about being "just" something. I was spurred on to share my new perspective.

There are also countless opportunities to meet and connect with educators around the world (well, mostly the US). There is so much value in this for all of us and our students who will benefit from these connections. I made a concerted and deliberate effort to seek out new people and talk to some who I wouldn't have otherwise spoken with - including the CEO of ISTE! I made several great connections which will help me make further connections in the future. It's all about the people. If that were the only result of the week in Denver it would have been worth it completely.

On top of meeting people at official conference events (probably the best source of that was the Global Ed Day - a great group of people to connect with, if you're looking), there were several social events which turned out to be just as valuable. I had made it my mission to find the "seedy underbelly of ISTE" this year, and while it definitely wasn't seedy, it made the conference that much more impactful. My only regret is that I didn't find more events to go to. In all, I attended events put on by Wonder Workshop (happy hour at a restaurant), the Ed Tech Team & Symbaloo (Karaoke), Gaggle (a party) and OSMO (a Sneak Peak event). All of those events, helping to strengthen my PLN (personal learning network for the uninitiated). I was able to build on some of the connections I made a year prior and hopefully will be able to build on these ones in 2017 (because yes, I'm going).

New Things and Old Things with More Pizazz

Having been at ISTE last year, I found that there were a lot of things repeated, but with more development. There were literally tons of resources (if you weighed them all together, there is no doubt of this) showing how makerspaces and making can be used in the classroom. Many people were sharing how they've been using their robots (many of which I bought last year after ISTE) and other cool gadgets in the classroom. For example, there were many people sharing what they've done with paper circuits (a shout out to Chibitronics & Spark Fun who both gave me some free samples to use in my classroom) as well as robots (guess who won a free kit from Hummingbird?) One really cool startup that was sharing in the expo was Hyperduino which had some really simple applications with their custom built arduino boards. They ran out of free samples by the time I got to their booth, but I may pony up the dough to get one.

It seemed like everyone had a Dash & Dot, Sphero & Ollie and Ozobots. Not to mention Makersaces. Perhaps this, too, was one of my big takeaways from the conference, and (since it's taking me forever to write this reflection) one of the things I've been most active promoting since I've returned. While I'm fully trying to gear up my classroom's Makerspace, ISTE this year has planted the seed of a big idea in my head. I'm working now to start #MakerEdNZ, a community of schools and teachers who are using Makerspaces in their classrooms. I'll write a long post about it later, but for now, just know that ISTE inspired me.

Global Connections

The only actual planned event I went to at ISTE was the Global Ed Day 2016. What a great group of people. Again, this is something I want to explore in much greater detail. Yes, we've done Twitter chats and Mystery Hangouts, but those connections are only on the surface (but again, much, much better than no connections at all). A lot of the talk around the Global Ed Day was starting collaborative projects between schools on different continents. This is another area for leadership within New Zealand, I feel, and something that is many people are primed for. We'll see what comes out of this, but perhaps someone reading this will take the call to arms and run with it. I only ask that you please include me.

Things I've Been Using

So it has taken me 2 months to get this far in my reflection. But that provides a great opportunity to reflect upon how those new things are going. Probably the most immediate thing I tried was Seesaw. For anyone who hasn't heard of this before, I urge you to have a look at it. I was lucky enough to have it explained to me by a teacher at the Seesaw booth in the expo. It's basically like Facebook for schools. Using the app (on tablets, phones or chromebooks) my students can take pictures or videos of their work, record an explanation over top of it, tag themselves in it and just generally share their amazing ideas. They can like each others' work and make comments - both written and oral! And I've only scratched the surface of what I can do with it. So far my students have found it super easy and have enjoyed sharing.

I also re-met my good friends at Kiva, which got me back to teaching the Kiva U curriculum (in the small amount of time that I can fit it in).'

I've also given my students focus with the Student Blogging Challenge. Though we may have been a few months late, meeting some of the people who have set this up, got me intrigued. My students have had some ups and downs with it (some of them spent a whole week or writing time making an avatar, not saving it, then making a new one), but overall it has helped teach them about blogging a bit more.

Another, practical thing I saw at ISTE and brought back to use were all the paper circuits that were being shown. I was extremely lucky to have been given those starter kits from Chibitronics AND Sparkfun, so I had a go with that at school AND at some educamps. It was interesting to say the least and something I want to look more into.  I was also given the chance to make a wearable circuit with some Lilypad Arduino components:

One of the sessions I went to was actually done as a walk around Downtown Denver. The presenter was telling us that we should be getting our students more active in class, and building movement into every activity. I had previously had swiss balls in my class but had given them up because of some behaviour issues. However, he inspired me to pump them back up and get my students moving more often. A small thing, but I think it's something that's important.

Conclusions

I could go on for pages and pages talking about how ISTE has changed me and my practice, but my biggest advice is: Go next year to San Antonio! It will change so many things about how you see teaching and give you so many ideas to help you do so. It will give you connections that will change your idea of teacher-teacher relationships and the way our profession should interact. It was honestly the best four days of the last year for me. Unlike a lot of the New Zealand based conferences that I've been to, ISTE has made me feel that we lone nuts are much stronger in numbers. It's nice to have our smallish group here, but expanding beyond our shores, in my opinion, is never a bad thing. Being part of something so big, is truly empowering. Meeting so many genuine people who only want the best for their students is inspiring. So, I urge all of you Kiwi teachers (and why not all my Canadian teacher friends as well, I belong to two countries), come with me next year! Come join my tribe!

Educamp Auckland

This past Saturday, I attended Educamp Auckland at Aorere College. I was quite nervous because, though I had attended two Educamps previously, this was the first I was going to stand up and share (though, I guess I did share at Sparkshop, but that was slightly different).

The nervousness turned out to be unnecessary, as everyone was amazingly supportive of me and what I was sharing. I guess I have become accustomed to people shooting me down and trying to get me to stop sharing.

I ended up having two sessions out of the three, which was good, but it also meant that I missed out on what a lot of other people were sharing. Though, the conversations are the best part (for me, at least) and I had lots of those.

It was also the first time where I publicly talked about my pet project: #MakerEdNZ. No doubt I will be sharing more of this along the journey, but suffice it to say, I was also overwhelmed by the support I got from many of my twitter friends (I guess they are real-life friends now). If anyone is interested in what this might be (i.e. if you know or want to know about makerspaces) please follow @MakerEdNZ on twitter (or me) and information will be coming out soonish (and probably another post on here as well - when I get caught up).

I did get a number of takeaways from the unconference. The first is (and I can't say it's the first time I've realized this) that I can easily go a bit too fast when sharing what I know. This is something for me to work on (but hey, I'll likely get a chance each of the next three weekends, so there's that).

I also have a few twitter chats planned with other people. It's amazing how quickly things can happen when you're in the right company. I'm excited and a bit nervous for this, but looking forward to both of those opportunities.

It was also a really great experience (going back to #MakerEdNZ) to give others a chance to spend some time doing some STEAM activities. I brought some copper tape, LEDs and batteries to make paper circuits. This is part of what I want Maker Ed NZ to be doing, so it was a good first step (though I wish I would have gotten some more pictures for the twitter account.

Steaming ahead with #STEAM #educampAKL @mrs_hyde @DianaWilkes @michaelteacher pic.twitter.com/4j0oNmST0E

— Caroline Bush (@CaroBush) July 30, 2016

If anyone reading this has never heard of an educamp, I strongly urge you to go to one (educampBOP is this weekend). Thanks to Jackie Allen and Stuart Kelly for all their organization of the day. Was definitely a positive way to spend my Saturday!

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.

Code Club Week 4: Girl Power Rising

Code Club keeps chugging along. Most of the issues that are coming up are minor - and related to my (mis)management of time. That being said, the majority of the students in the club are just coming in, doing the activities and then leaving. It's a bit like herding cats at times, but I'm not too worried. I wanted to give students an opportunity to code and LEARN some coding. I feel like I'm achieving that. I don't need to limit them by stopping. I will be trying to share a bit more.

One thing I want to talk about is girls in coding.

A common theme today is the lack of women in coding/computer based jobs and being represented in university Computer Science programs. I could cite many different articles (ok, I will: here, here and here for starters). Without going into the various reasons behind this, I feel like as a teacher I should try to do something to correct this balance. Why can't my girls gain these skills and enjoy doing it?

Will one Code Club at a school in New Zealand make a dent in the statistics? Probably not. But the message, once spread might. I've always thought that as a male teacher, I brought some value that my female colleagues could not bring (that's not to say they don't add anything that I can't, but there are far fewer males teaching young girls and having a positive non-relative male role model is quite rare for girls) - namely that I could encourage them, as a male and show them that it is a valued skill in them. I'm hoping that my job is one of keeping the flame lit, rather than re-igniting it.

Have I done anything out of the ordinary for the girls in my club? Not particularly, except I've encouraged them (which, I guess, could be more encouragement than they're getting from other sources). I was quite pleased with the number of girls I had this week. On Tuesday, I had about 3 times as many girls as boys. And honestly, I don't see any difference in their ability to code. One of the stars of my club is a girl in my class. I don't think she has a lot of experience, but she is enjoying it and has been eating up every new thing she can - she even comes both days I hold the club. That's dedication.

In my search to find information about this, I also found some resources for anyone interested in encouraging girls to code. Here are some of them:

• Girls Who Code
• Code.org
• 100 Girls of Code

I feel this is a very relevant area in all things STEAM. I'm not sure what direction this will lead me at my school this year and beyond, but I do have some plans. If you've got some girls who are really good at coding, there is always Lilypad Arduino as well that can be used to make wearable technology and clothing - though boys can play with those too. I've ordered some and am in the process of trying to figure out how it works (because as much as I may know about coding, it's not really that much.

If anyone has actively gone out and promoted girls in Coding or STEAM, I'd love to hear from you. I may not start implementing new ideas in the coming weeks, but every idea is a spark that is very hard to extinguish in my head.

I look forward to hearing from you!

Code Club: Week 3 - Starting to Get the Hang of It

It's week three for my school's Code Club, though we're only up to Activity 2 after our tech issues in week 1. After getting an email from cs-first telling me I haven't been using the showcase selector, I thought I had better get onto it. Trying to fit an hour's worth of activities into 50 minutes (more like 45 when you count the transition time) is difficult and sharing was one of the many casualties in the first week. Many students didn't really get it and having some success stories to share might help.  So I made a point of getting students to share their work at the end. The selector wasn't actually working, but by playing around with the site, I was able to find a way to find the students' work (provided they had pressed "share") and put it up on the board. Though as I type this I realize that my projector has just been taken out of my room (we're moving classrooms this week) and I won't actually be able to share with my second lot of students.

I've also noticed that several children have come to me and said they want to quit (with a few more just quitting and not telling me). I'm OK with this. I don't want to force anything on anyone. I want to have students who want to code. I'll let them come back if they want (and perhaps some of them left due to my unpreparedness), but for now, I'm happy with some smaller numbers.

This week there were a larger number of students who weren't lost in scratch, so I did actually have a few examples I could share. Here's one from one of my own students. She was really focused on the videos, and asked lots of good questions (she figured out, before the video told her, that the words were being said at the same time, and then watched the next video to figure out how to do it). This is her project (she has asked to come back today for the second session to finish it - gotta love the enthusiasm!):

Code Club: Week 2 - Blast off!

After sorting out all of our problems (the videos were being blocked by something or other) we were finally able to have a genuine code club this week.

I was feeling a lot less stressed about the club this week as the attempted club last week helped me wrap my head around how the day works. That being said, I realized that there was no way I could talk in front of everyone as much as the script said and still get through everything.

Over two days we had about 40 or 50 students (it was tough to find time to count, as you'll see below) coming from Years 3-6 and with a varying degrees of coding experience. Generally, I was pleased with how things went (how could it not be an improvement from last week?), though there were still some issues that will require some ironing out (or at the very least, perseverance).

One thing that was obvious from the get go was the level of independence that some students had (or rather, lacked). Most of the year 3s were constantly asking questions about what to do next (even though there was a button on the screen that literally said "next"). This learned helplessness is one of the things I'm battling (I should give myself a superhero name: Captain Independence, helping children become independent learners), so this is a fantastic opportunity let children have a go at it alone. So if you're doing a code club, be prepared for this potential time eater if you've got younger children. I'm not saying don't have them - far from it, they need to learn these skills and this should help them.

The second issue is a bit more worrying. Many students (both experienced and inexperienced) would put up their hand and tell me: "I'm finished watching the videos," as if to say that they were done. None of them had actually listened to the videos and done the activities. Others would watch the video, start the project and play around with things without trying the actual activity. I guess this is two sides to the same coin, but both are essentially the same problem: they don't follow instructions. They want to play (or just know how to do something) without the knowledge that will help them. It's about instant gratification vs delayed (by something like 2 or 3 minutes) gratification. I need to help teach the students about using the resources they have to learn something AND THEN having a play and discovering.

These are thoughts I will be pondering over the weekend. Do I want them to play? Yes. But not at the expense of learning a skill. Perhaps that will one day be the focus of my code club, but right now, they're not experts (is anyone, really ever an expert?) and they could benefit from learning how some of the blocks work, rather than just doing the same thing (usually just changing the avatar of the character) over and over.

Code Club: Week 1 - Technical Disaster

As part of my role as eLearning Leader (though, to be perfectly honest, I would do this regardless of roles or responsibilities) I have attempted to start a Code Club at school this past week. I sent out a form to get students to enrol and got about 60 students who were interested! With such a huge number I decided to split them into two days.

This has been a thing I've wanted to start for a while, but until recently I have not been sure how to go about it. Then, with the help of a presentation at the GAFE summit, I was introduced to cs-first.com, a google resource. I had heard of this before but never really gave it a chance (so many other things going on, and Code.org was pretty awesome for me at the time - still is, in fact). So when we tried a sample lesson a few weeks ago, I was blown away by how simple it was to a) run the club and b) learn new concepts. Google has really done a great job at preparing these coding sessions.

So I went through the process of setting up two clubs, sorting out the children (which still, will need to be changed) and getting everything ready. When we initially checked that the site was working, we did get most of the videos to play. I assumed (does this phrase ever end good?) that that meant that all the videos would work. The morning of the club, I was checking out the day's plan and couldn't get the needed videos to play. We tried on other computers in the class. No dice. So frantically, I emailed our tech support. They looked into it. They fixed something. No change. They fixed something else. Still no change.

The one bonus was though, that most of the children came late on the day. I had 7 students. I was able to help them through a part of the lessons to work on their code. But the next day, things still weren't working, so the second session was postponed.

It took almost a week, but the tech guys figured out the problem (by that time, I was interested in what it was, I was just super relieved that it was fixed. So code club will be on next week. Which is good, because the small group I had helped me get a trial run of what it's supposed to look like. We'll still be crunched for time, but that's better than nothing, I think.

I guess the moral of this story is: When you assume....

Educamp Science

Introduction
This Saturday morning, I woke up early to run so that I could go to the first Educamp Science unconference. Luckily for me, it was local, so I was able to enjoy the sunshine before the conference. Having been a chemistry major before I went into education, science has always been something I enjoy. I got to meet several of my twitter friends early in the day and there were lots of choices for breakout sessions.

Data Logging with Stuart Hale
The first breakout session I went to was about Data Logging. The first bit of the talk was about using pictures, since they are a large part of collecting data in science. Stuart showed us how to share between devices when no wifi is available (through airplay on the iPads) as well as showing us how you can use a loupe (a magnifying glass for jewellers, if I'm not mistaken) to make a really cheap digital microscope. In fact, I was able to find loupes online for even less than what he shared. All you need beyond that is some blue tack.

Another neat thing he showed us with the iPads is to use the built in Time Lapse feature on the camera app. You can put it on things, such as leaves, construction sites (I'm trying that now in class, with the builders behind our room), tides, etc to see how things change over time.  He suggested putting a sticker in the corner of the iPad where the camera is, to help children who might put their finger in front of the lens.

Digital Microscope with Wooden Blocks as a Stand

He then went on to show us some really cool things that iPads can do. Most iPads have the ability to measure things such as vibrations (a seisometer), magnetism (telsameter) and acceleration (accelerometer). These things can be use to make graphs and conduct scientific investigations (he used an iPad to test what makes a bike ride smoother as well as to see how to make sturdy buildings).

On top of that, there are loads of sensors that can be purchased (temperature, movement, etc) that can be used to make graphs. PASCO was the company he suggested, though I imagine, a quick internet search will provide other, cheaper options.

Fischertechnik Makerspace with Jacqui Kao

The next session I went to showed us about some makerspace tools that you could use. The company that makes them is called Fischertechnik. They have reusable parts, which can be really useful in a classroom or for companies that don't want to spend money on something that might fail and be very expensive.

During the presentation, there was an interesting discussion on buying kits vs. buying parts to make things with. Both have things that can make using them prohibitive. Kits can be quite expensive, BUT buying parts can be a very daunting task for someone who is just learning how to use these things in a classroom. It was a good discussion, but I think the answer is a lot more grey than it is black or white.

An interesting website was shared during this presentation, that I hope to look at later: Thingiverse. The site contains a lot of pre-designed things (for lack of a better word) that can be printed out using a 3D printer.


Maker Spaces with Chris Clay & Mark Mack

The last session I went to was a discussion about maker spaces and maker clubs.  One of the teachers from Elim shared with us a project one of his students completed: a word clock. The student came and they discussed the process and challenges they faced in making it. The one student alone put about 60 or 70 hours into the project (which was quite impressive, as shown below). One thing that did come out of this discussion was that the original club had a lot of members and they all were working on the same project. Over time, the numbers dwindled until it was just the one boy who ended up finishing it. The teacher spoke that perhaps it was too difficult of a project to START with (not that it was too hard, there is a difference). So, big ideas are great, but aim for them one small step at a time.

Then Chris Clay (of Mind Lab fame, when I was in their course) spoke about making robots out of recycled materials which could cost less than $25. He uses Arduino boards and imports most of his parts from China (like I've started doing recently). He showed us several models he had made and discussed the challenges. He is one to keep following for tips about this as he has spent the last few months, testing and prototyping lots of different things and is in the process of helping schools along their journey. He spoke of a new way to program Arduino (I haven't learned the original way yet!) which is much like Scratch.  It's called Snap.

Another thing that Chris (briefly) showed was Lilypad Arduino. I have heard of this before and was considering it. It's a small arduino board that can be sewn into clothing to make wearable technology. I've ordered some of these parts to have a play with so hopefully that will be another post on this blog in the near future.

 Overall, it was an interesting day. Most of the things we talked about I had some knowledge of, but each session helped me build on that knowledge and has pushed me even further on my journey. I've got some more confidence to try some new things.

Also, I find that spending time in the real world (as opposed to the virtual world of twitter and blogs) is quite beneficial for my thinking process. People share ideas, ask questions and challenge me. I'll definitely keep attending more of these unconferences!