I was a kid in the 80’s, the short-lived golden era of Home Computers. I had a Sinclair ZX81, followed by a ZX Spectrum 48K (and another one when that one broke). At the same time I also had access to a very nice Commodore CBM 8032 and a BBC Model B at junior school. Later at home we got an Acorn Archimedes A440, later replaced with an Acorn RISC PC. At my senior school at the time, we had BBC’s, later replaced with a whole suite of Archimedes Machines.
Most these computers shared a common feature – when you booted them they presented you with a BASIC prompt. You were expected to enter code. Most children at the time could write a two line program (you know, the one that starts with 10 PRINT and fills the screen of the TRS80 in Tandy with rude words), and the computer rooms were usually fairly busy with people writing code. Even the Archimedes, recognisable to a present day user as a “proper” computer, had the superb BBC BASIC V right under the skin.
I spent a lot of my childhood tapping out code, and ended up working as software developer. Would I have done the same without these funny little computers? Who knows! We had no formal computer teaching of any kind at school. If you were lucky, there was an enthusiast teacher who might be able to answer a question. No Google either of course!
Unless you live under a rock (or outside the UK) you’ll have noticed the sudden rush of media coverage on the topic of ICT and IT teaching in schools. To me it felt like it all started in the media when Eric Schmidt criticised the British education system. I’ve been moaning about this to anyone that will listen for a several of years now, but actually did nothing more than that. Thank god some people have been more organised: the Raspberry Pi foundation (including the legendary David Braben), the Next Gen Skills group, Ian Livingstone (of Fighting Fantasy fame) and Alex Hope of Double Negative who co-authored the Next Gen report, the Royal Society’s “Shut Down or Restart?” report, the Computing at Schools working group (who published a rather good free suggested computing curriculum (PDF), the Goto Foundation, Rory-Cellan Jones (the BBC technology correspondent), the Guardian’s Digital Literacy Campaign, and probably other I’ve missed. The tireless efforts of these campaigners got the media covering the issue, and that meant the government had to respond, which they duly did.
There’s a lot more work to do, but it’s wonderful to see the energy and enthusiasm erupting here. I also think it’s wise to be cautious about the government’s response, and to recognise the good work that’s already being done in schools.
- The ICT suite has all XP machines, very locked down, and it’s hard to install any software on them.
- They only have IE installed, which rules out a lot of good web-based material.
- The network uses a problematic (in the words of the IT Administrator) firewall/filter appliance which makes it hard to access sites, since every domain they hit has to be whitelisted.
- How to set up a platform I can really work with on the machines, without causing problems for the IT staff.
- What to cover. I think I will have to play this by ear, depending on how many turn up, what their skills are and what the are interested in.
- How to give the kids a way to carry on the activity between weekly sessions.
- How inclusive it should be.
This last point is one that bothers me most, going in to it. Programming is quite hard, and requires patience and dedication. Some of them will probably have big, unrealistic expectations about what they can achieve, and I need to adjust those gently without putting them off.
When I was a kid, I got a buzz out of figuring a puzzle out, cracking something new, making a piece of code work no matter how simple. That buzz is the payoff that you need to keep you there through all the frustration and effort you have to put in. If you don’t get that, I don’t think you’ll go on to be a developer.
So, I hope I’ll get a few in the group who are the real deal; potential software developers. What about the rest? Do I try to put them off? Keep them entertained and hope a few things will stick? Because this is a club, not a lesson, I can play by different rules. While I believe some of this should be in the curriculum, and that all kids should get a grounding in it, this is an enthusiast group.
The ones who are the few who will stick with it will probably be happy writing Python code to print the Fibonacci sequence. The ones that aren’t will want whizz bang eye-candy to keep their interest going.
So how to balance it? Can we keep everyone happy?
Any advice welcomed!