Friday, 5 August 2022

Starting a Code Club!

As discussed earlier, I'm expecting to be starting a new Code Club in September, at a secondary rather than primary school. This will be more challenging, I hope and expect, because of the age range and increasing teenager-ness. 

Budget?

The staff member leader says she has a small budget for this, but had thought of using Lego-based programmable stuff to provide a bridge from their possible learned experience for Year 7 students. I investigated this, and even the cheapest Lego automation kits for schools (no longer Mindstorms, but Lego Education SPIKE) run at £200-300 to support just two students. So that doesn't seem sensible. 

Meanwhile, over at Science Oxford, where I've been volunteering recently, the leader there has a huge wealth of good experience with stuff purchased from AliExpress etc., as raw materials or boards that are relatively easily, and experientially usefully, assembled into robots or other automated/controlled entities, for far less money. Excellent. 

It's worth looking at the Science Oxford GitHub repository for lots of projects that Sarah has run over the years. Of course, not all of these folders provide the recipes for components etc., but they're good for starting points. 

I certainly think it's worth looking at setting up a store of various controllable objects, like motors, servo motors, LEDs both raw and NeoPixel-like, and their associated control boards for microbits. Bought in bulk from AliExpress, they are pretty cheap. 

Topics?

I was thinking it would be best to start simple, by surveying the assembled multitude for their existing knowledge and possible ideas/enthusiasms, whilst giving them a starter project initially, probably on laptops only, or with microbits on their own, no added materiƩl. Get the right atmosphere, one of exploration and non-judgemental experiments, and they should flourish. Ideally, there would be multiple individual or small group projects running over a period, so that students are pursuing their interests with the enthusiasm that brings, rather than me excessively imposing my ideas. It would also allow for everyone to learn from everyone, as there would be examples of problems solved for all to see.

The Code Club website has bazillions of projects and learning paths, I've no doubt I'll be drawing on those. Letting kids find their own way so they can proceed at their pace, and get a blast from explaining to you what they're doing and why, whilst knowing that they can get help and explanations is a good result.

Let's see how it goes.

Washing Machines as a topic for CC exploration

I'm about to start a Code Club at a local secondary school, courtesy of a couple of days as part of the STEM Network. That involved working with Year 7 students on a "make a security device/container" project, using microbits. One of the staff involved asked me if I was interested in supporting a Code Club, what could I say?? Anyway, some ideas for entertainment may be required...

And in respect of that, how about designing/building a washing machine?? Not a fully functional one of course, but at least getting the kids to think about what the requirements for a washing machine are, how they could be met, and programming/building some of the more interesting aspects.

Ideas include:

  • Water Temperature (variable)
  • Heating control
  • Washing powder/softener/pre-wash release
  • Water valve controls, water height/volume
  • Motor speed, intermittent vs spin cycle
  • Wash Programmes (separate value settings vs. validity, or "packaged" programmes?)
  • All the interlocks (doors, water height, stop/start/reset etc)
  • Timers of all sorts
  • Front panel display and controls (content, complexity, UI aspects, warning sounds/signals etc)
  • The future of washing machines?? Online interface? Security concerns? Phone control app (using 
All of this could be coded on microbits, with physical "simulation" of some kind or other. It could be a multi-team/person project, with each group working on a different aspect, and having to coordinate.

More on this later...