Hi there, good to meet you folks!
My name is Sarah and I am the new Participation Manager at Code Club. Some of you might have already met me as I’ve been developing training materials and helping to deliver training sessions for volunteers across the UK.
So, what does this marvellous new Participation Manager do, I hear you ask? Well, training for volunteers is a part of my job, but my main mission is to onboard and reward volunteers. In other words, to make sure that if you want to volunteer for Code Club the process of signing up is as easy as possible, and that once you are volunteering you get looked after nicely and get all the support you need :)
The first thing I want to do is find out how our volunteers use the resources we already offer and what we could add or improve upon to make your experience as part of Code Club even better! I’ve set up Google Hangouts at different times over the next few weeks so we can chat.
If you can’t join me on the hangouts, feel free to drop me a line instead with thoughts or ideas about how we can improve the experience of volunteering with Code Club. Just send me an email: firstname.lastname@example.org
Also, if you’re coming to the Code Club Birthday Party in London on 30th April do come and say hi – I’ll be the one in charge of the cake.
Team Code Club cooing over Sense hardware and a Raspberry Pi
Last night I had one of the most enjoyable meetings in my short(ish) life. Linda and I headed to Mozilla HQ (who had kindly lent us their big meeting room) to meet the the newest members of Team Code Club who we’d asked to help us write the curriculum for Code Club’s first term. Neil Smith is a lecturer at The Open University in the computing department, Adam Onishi is a front end developer at One in Oxford, Alex Rosen is an ex computer science student, developer and co-founder of Breed and Craft and Josh Emerson is an awesome front end developer at Clearleft in Brighton. We’ll also be consulting with Aral Balkan, Seb Lee-Delisle and Dr Sue Black remotely as we reach critical stages in the development of the curriculum.
We looked at the current Scratch curriculum guidelines and discussed what we’d like to change and add to it. We’ve decided to create small projects that can be completed at a rate of one per session with varying levels of difficulty. We’ll be creating four lessons to begin with, these will then be tested in our 20 pilot schools to gain feedback and insight into what works and what doesn’t. The pilot lessons will be in test schools in time for the last half term of the year before the school summer holidays.
It’s a privilege to work with such skilled and enthusiastic people. This is going to be A LOT of fun!