micro:bit code printout

The Village of Banton, where I teach, celebrates Halloween on the Friday before the 31. Which is nice ’cause you can have a Friday party. We had one yesterday afternoon, in the morning we did some halloween related work.

When I sat down at my desk yesterday morning I had a quick look at twitter. I’d been in a conversation over breakfast. I ended up having a quick scroll through Mr Morrison‘s timeline. I saw a couple of interesting micro:bits things:

https://twitter.com/SSERCDigital/status/1585251905428918272

and

The first was to blow away a ghost. I couldn’t see instructions, but presumed it would be simple enough to figure out. The second was really simple, but linked to a blog post which had a nice wee pumpkin cardboard template that fitted a micro:bit.

Pumkin Ghost

My class have done a varying amount of coding, so I though we could do this as a stepped challenge. The more experienced could help the other out.

I printed off the templates and cut out the holes for the micro:bit buttons. I’ve found that making a neat job of these is difficult, but helps keep the cardboard on the micro:bit. Quite glad I’ve got a small class.

I then worked out and made the code to, add a face to the pumpkin with button A and a ghost with button B. Blowing on the micro:bit would blow (animate) the ghost off the screen.

I made a quick slide with the challenge and pictures of a few useful blocks.

Microbit Halloween Challenge: 1. Show a ghost for pumpkin on button a 2. Show a face on button b 3. Animate face 4. make ghost go away when you blow 5. make ghost only go when it is already on screen 6. play a sound when ghost flies off

We started the lesson by being really quiet and watching me demo. The class is 1-2-1 iPads and we use the micro:bit editor, we have enough micro:bits for one each too.

My though was that the least experienced could manage 1, 2 & 3. I hoped the images of the blocks would remind the others of enough to get them started on the harder ones.

Most of the class managed the first couple of tasks straightaway. To my surprise quite a few asked to skip the third. The vanishing ghost was too tempting.

The next step, to animate the ghost away on a sound was managed by quite a few of the class. The tricky part was only showing the animation if the ghost was on the screen. A few, having seen the clues on the slide, created variables to test for at the start of sound block. We did need to stop a few times to figure out when and where to toggle the variable and how to test for it in the right place. Lots of useful mistakes were made.

By this point a few children had managed to solve the complete problem, adding some sounds to their animation. They could then help, (without using their fingers), their peers. A couple of the class didn’t manage to get the whole thing done, not getting a full understanding, but they all managed at least some of the challenge.

Given the class have done at least a couple of recent micro:bit lessons covering inputs and decisions the challenge approach worked well. Some had used code that was not particularly efficient. Some strange and unnecessary repeats. I am not really sure my own approach to the code was the best.

As everyone put the finishing touches, cutting out pumpkins and tweaking code I though we could finish with a quick demo of the radio feature. For this bit I did just put the code up on the board.

One child, remembering radio code from previous years volunteered to make the controller. We finished by testing and recording the radio controller, setting all the micro:bits to show a ghost via the controller and getting all the ghosts to fly off by shouting boo!

A few interesting points emerged

  • This idea came to me though some tweets at around 8:00am I had to through some resources together before 9, scrap (recycle) some of the morning plans. The final section, using the radios, just came to me while teaching and extended the process by half an hour. I am sure this says something about my professionalism & planning.
  • Working through the logic is hard. The children with more experience are beginning to be able to debug sometimes. Noticing typos (or bad values for variables, blocks avoid a lot of these problems) you have made or miss-ordering or putting blocks in slightly the wrong place is easy. I was listening to a WordPress lesson driving into work on Friday and noticed that the tutor, presumably prepped and a confident coder, still made mistakes like these.
  • Somethings just didn’t work. Adding sound work if we used the play sound block with pre add sounds. Using the melody block or the block that plays sounds you write yourself tended to cause problems. All the code would stop working after a while. I am not sure if it is a bug or problem with the micro:bits or we just don’t know something.
  • A couple of pupils had exactly the correct radio code but it just did not work exactly as expected. The code used an if else block to switch depending on if it received a 1 or something else. The micro:bits just executed the first choice every time. The pupils and their pals couldn’t see any problem with the code and neither could I.
  • Most of the class wanted to get to the more dramatic bit of code quickly and asked to skip the simple animation of the face. Quite a few wanted to work in the code editor without testing their code until they got to the end. I was quite happy with the skipping bits but I did ask them to do quick tests as they went along.
  • One pupil who had got into a bit a mixup with the code had made a nice change to the animation, the ghost going off the screen at an angle rather than straight up.

The micro:bit editor has a nice print feature, I used it to make the featured image for this post.

Listened: OEG Voices 040: Charlie Farley and Lorna Campbell on Two Award Winning Projects from University of Edinburgh – OEG Voices a podcast produced by Open Education Global.

I huffduffed 1 this mainly to hear the voices of Alan & Lorna.

A few years ago I really hoped that the OER idea would catch on with primary & secondary teachers. Ian and I discussed this many times while working on Glow. We went to a few OER and Wikimedia events but we never got the traction to make it work.

Sharing resources for primary & secondary schools seems a very mixed bag of Facebook (I am lead to believe), the web, TES, twitter and Google Drive. The understanding of OER and creative commons amongst my colleagues is not evenly distributed yet. This is not a criticism, my knowledges of many areas I should know about is quite shaky.

I really enjoyed the listen, the work Edinburgh is doing is inspiring on all sorts of levels. I learned this included my own:

In this episode’s conversation, OER Adviser Charlie Farley shares a fabulous outreach program started in GeoSciences that has expanded to other disciplines, where students get applied open education experience working with local schools, museums, and community groups, to design and publish OERs that are shared openly through TES Resources and Open.Ed.

This has taken me to University of Edinburgh Open.Ed – Teaching Resources – Primary Science which looks as if it is full of a lot of useful resources for me and my school colleagues.

The ones I’ve downloaded so far are well badged with Open Education Resource and Creative Commons licenses. They also look like great resources.

I am fairly embarrassed not to have known about this, but quite excited I do now. I’d recommend a listen for inspiration & following the links for useful resources.

  1. Huffduffer is a wonderful service that allows you to gather audio from across the web into your own personal RSS feed. You can then subscribe to that in the app you listen to podcasts on. It also will rip youtube videos to audio and add them via huffduff-video

I saw a tweet from  James Abela:

Just found this amazing tool to convert any @scratch project into a #Mac #App. You can now literally use this kid’s tool to put apps together! Incredible and I managed this in less than a minute! #everyonecancode #scratch #appinamin #coding How to make a Scratch Project into a Mac OS app in under 1 minute – YouTube

The TurboWarp Packager Converts Scratch projects into HTML files, zip archives, or executable programs for Windows, macOS, and Linux. but it is linked to several tools that are part of TurboWarp:

TurboWarp is a Scratch mod that compiles projects to JavaScript to make them run really fast.

Now the sort of thing I do with scratch is certainly not in need of speeding up or turned into an application! But I have seen many really complicated scratch programs, but my needs are simple.

I did recall a maths project we made in class a couple of years ago, when working on probability & chance. The project throws dices a number of times. Of course the class wanted to run it many many times, but it got a bit slow once we got to 10 million throws.

Here is the Project on Scratch:

And in Turbowarp:

For me 100 million throws took 1056.443 seconds in Scratch and 21.784 seconds in Turbowarp. I guess device, browser, operating system and the direction of the wind might change these results a bit. I also expect the code could be a lot better;-)

I listened to VR, the metaverse and education by Edtech Innovators which interviewed my pal Ian Stuart.

Apart for a little dip into Google Expeditions a few years back (eek!) I’ve not really paid much attention to VR.

Of course I’ve read a lot of tweets from Ian who is now working in the VR field, but not dug in. So I was interested to listen Ian talking on this podcast. It is well worth a listen, a quick 30 minutes.

I liked the way Ian linked VR to his previous use of technology. Ian insisted that the technology should be developed in response to classroom needs as opposed to the repurposing of business software. Ian had some nice examples of the use of VR and touched upon its use as part of project based learning.

Ian also mentioned an experience from his Islay past, when project based learning needed a fair bit of scaffolding to get off the ground.

VR does not come naturally to me. I did see how engaging it was for my class using Google cardboard back in 2016. We didn’t have the time to get past engaging to learning but Ian explained some of the ways it could be added to real learning.

Ian pointed to Eduverse The World’s First K-12 Metaverse where there is a fair bit of free content to explore even without a headset. I’ve only had a short browse in my browser, but I think I’ll see how well it runs on our iPads on the school network.

Side notes:

  • One of the things that puts me off is word Metaverse, it is so linked to Facebook I naturally balk.
  • Anchor/Spotify is a pain to winkle podcasts out of. I add episodes of show I want to listen to, as opposed to sub to the whole series, with Huffduffer, it relies on an mp3 being linked to in the episode.
  • Ian should have had a blog for all these years he has been involved in interesting things.
Bookmarked Data logging with the BBC micro:bit (microbit.org)
You can use the BBC micro:bit V2 with built-in speaker as a data logger, recording data from its built-in sensors. Data is stored on your micro:bit even when its power source is disconnected.

This looks really interesting. H.T. to @LouiseE_Foreman. The way the data is saved and accessible is very clever.

You can log data from any of the micro:bit inputs; light sensor, temperature sensor, pins, accelerometer, compass, microphone

 

Replied to The startupification of education (werd.io)
But not everything has to be scalable; not everything has to be venture scale. There are a lot of public services, technologies in the public interest, and fully-profitable businesses that benefit by not trying to reach scale. Relationships are the building blocks of society; eradicating those in favor of analytics, in education of all places, is counter-productive, to put it charitably.

This is a wonderful post Ben, thanks you.  It speaks, to me as a primary teacher, to more than just EdTech and startUps. The big internet beasts have some claws in education and seem to be working towards what you call the  rat-maze simulation of intimacy. Governments seem bent on datafication.

Technology can be part of informal & formal personal relationships. The technology I find interesting is messy engaging and has not much to do with scalability & market share.

In my tiny world, I hope technology helps inclusion, engagement, diversification of approaches and fun. The presentation & recording of learning in a useful way by learner that is still individual, not auto analysable and open to conversation.