Thursday, 10 February 2011

100th post

"I have come to the conviction that if you cannot translate your thoughts into uneducated language, then your thoughts were confused."

You're damn straight, CS Lewis.

Friday, 4 February 2011

Optimism, pessimism, and problems


This is something a friend of mine said today:


"I like problems because I'm an optimist.

"When I find a problem, I talk about it and I find lots of parts to the problem and I go over and over how bad the parts are. It annoys people, because they think I'm complaining.

"I'm not complaining. Complaining is the response of someone who thinks a problem can't be fixed. What I'm doing is working it through. I talk so much about how bad the problem is because my underlying belief is that the problem can be fixed.

"Responding to a problem by smiling and saying 'oh well, can't be helped', that's the action of a pessimist.

"I'm an optimist.

"I like problems because I'm an optimist.

"Because I'm an optimist, I like problems."


Now I've misquoted him a lot (that's what you get for not taking notes in conversations), but that resonated with me. Actually, it's a long time since I heard anyone say anything that rang so true.

Because I like problems too.

I always thought that made me a pessimist, always looking for the faults in everything.

But maybe not.

Monday, 17 January 2011

ICT in high schools

Last Friday I went to the be bettr conference - and what a terrific day that turned out to be.

There were many presentations worth blogging about - Manga High for game-based maths looks terrific - but the two that really caught my eye were by Aral Balkan (@aral) and Anna Debenham (@anna_debenham). Largely because they were both talking about the same question:

What is wrong with ICT in schools?

Answer: Lots. But I think it can be boiled down to an even smaller question:

How do people learn how to code?

...and boiled down a little more, burned to the bottom of the pan but still kind of tasty:

How do people learn difficult skills?


Apéritif

I strongly recommend you all check out Anna's presentation on what's wrong with web design in the UK curriculum. Skip to slide 29 for the single most ghastly piece of design you'll ever see - one that would get you an 'A' in your GCSE.

(And for your unicorn chaser, check out her site at www.scrunchup.com - shame hats on, mature geeks, the lady who built that is about 20 years old. Which is why my poor blog is finally going to get a makeover. Because of the shame.)


Entrée

Now this is something I care about a lot. And I care for one, very selfish reason: I have tried to learn code. And I have not succeeded.

...but actually, that's a lie - I can write regular expressions. And I can navigate Unix from the bash prompt, and write (basic) MySQL queries. I can beat non-well-formed XML into submission, even if it's written in accordance with some heinous standard (I'm looking at you, QTI 1.2 for Common Cartridge). I can even -sometimes - diagnose problems with SCORM packages, about which the less said the better.

But put me near Perl, I've got nothing. Ditto writing (as opposed to wrangling) XML, or even (shame on me) CSS. I've got nothing.

Which is frankly ridiculous, because I've been trying to learn them - intermittently - for EVER.


Main

There's a basic divide between the skills I have and the skills I want: The skills I have are things I had to learn to do what I needed to do.

The conclusion I've come to is quite simple: I do not have the ability to learn technical skills unless I'm actually *using* them. I know I have the aptitude to learn CSS, but I haven't, because I haven't had cause to use it yet (yes, yes, hello terrible blog design, the irony is not lost on me.)

I saw my experience reflected by Aral, who learned code by beating the hell out of his computer as a child, and Anna, who learned code through neopets and myspace. They could both see something that they knew they wanted to do, and worked out how to do it. Having worked out a bit, the bit they knew lead them to new things they wanted to do, and so the spiral expands.

So I think we can break this down. Successful acquisition of technical skills (for the three folk mentioned here, at least) relies on three things:

1. Wanting to do something
2. Knowing enough to *start* doing it
3. Having a place to do it

...and I'm not seeing any of those in the ICT curriculum.


Dessert

Here's my proposal. All secondary schools in the UK get a special sandbox server. The server is accessible with a school-based logon (your standard Raven/Shibboleth/Athens, or whatever secondary schools use if they don't use that.)

And then we let the kids fill it up with the most awful nonsense they possibly, possibly can. Whatever they like, as long as they like it.

Malware-riddled free wordpress themes, animated gifs, awful, awful software dredged up from the very bowels of sourceforge. Anything.

If the school is a fan of permanent surveillance (most seem to be), they could pop a keylogger on. If they're freaked out by Scary Internet People, they could make *everything* password protected, nice and invisible and irrelevant.

(On that note... when I was a teacher, I used blogger blogs with my year 8 students, to teach English and a little bit of html (which I was terrible at, by the way - as it turns out, that totally didn't matter). They loved it. One kid loved his blog but didn't love the class rules, so he made an outlaw blog. It got a brief following by some not-from-the-school people who loved his stick-it-to-the-man/teacher style, which was especially good seeing as he thought he was rubbish at English. Amazingly, the world did not actually end because of this.)

And then, at the end of the school year, everyone who wants to download their work down can.

And then the server gets wiped. Completely. With MAGNETS*.

And then it's nice and tidy for the group next year to destroy it all over again.


Tiny delicious mint

...Actually, I think I might need one of these for myself. ;)


*Not actually with magnets.

Wednesday, 12 January 2011

Yay! Publication!

Well this has been fun.

After a decent amount of time in the wild world of electronic publishing, I have temporarily switched teams and become... an author!

It took longer than expected, and involved a certain amount of swearing (at myself, not at the good people of Backstop media who commissioned the article, or IBM developerWorks, who published it).

So, e-learning standards fans - here's a dose of 'Technical standards in education, Part 2: Learning technology standards, specifications, and protocols'.

Good times!*

http://bit.ly/gaacRa

*if you love standards, that is. Otherwise, probably not much fun.

Tuesday, 21 December 2010

Know your knowns

As I am on holidays, I'm catching up with the long list of 'things I've been meaning to blog about forever'. Today: Donald Rumsfeld.

"There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don't know. But there are also unknown unknowns. There are things we don't know we don't know."

- Donald Rumsfeld, 12 February 2002.

I hate to find myself defending the man, but this makes total sense - and it is a very powerful tool for knowledge management.

Let''s break this down. There are only two variables:
  • Known
  • Unknown
These two variables can be combined in only four ways:
  • Known Known
  • Known Unknown
  • Unknown Known
  • Unknown Unknown

Consider the potential applications as they relate to the knowledge held by a single person about "Bronywn's birthday"
  • Known known
    "It's Bronwyn's birthday tomorrow"
  • Known unknown
    "When is Bronwyn's birthday again?"
  • Unknown known
    "Crap! I forgot Bronwyn's birthday!"
  • Unknown unknown
    Bronwyn is actually a cylon, and therefore does not have a birthday.

...that's one person, but the same can apply to an organisation where knowledge is distributed across multiple brains - such as, for example, James Bond's nemesis organisation SPECTRE:

  • Known known
    (Everyone in the organisation knows what's going on)
    "Tomorrow we will hold the UN to ransom with our incredible Death Ray."
  • Known unknown
    (One+ person doesn't known something, but they know that someone else does know)
    "I can't find the keys to the Death Ray. Who has the keys? Come on, one of you guys has the keys..."
  • Unknown known
    (One person knows something, another person doesn't, but they don't know there's a disconnect)
    "The infra-dinfra-super-destructo setting isn't working, why isn't it working? Is it broken? I think it's broken." (It's not broken, the lead engineer turned it off on purpose because it was badly implemented and likely to explode/destroy the entire Headquarters.)
  • Unknown unknown
    Henchman #5 is actually James Bond. He has stolen the keys, invisibly set the infra-dinfra-super-desctructo setting to blow up in five minutes time, and is currently riding to freedom on the back of a robot dolphin.

Tuesday, 14 December 2010

Copyright in higher education is annoying

I'm going to go on ahead and pirate my own comments from Nicolas Steenhout's blog. I should point out here, however, that his post is better than mine - read it at http://accessibility.net.nz/blog/copyright-universities-course-content/

***************************************

It seems to me that there's actually a schism at the heart of copyright in HE lecture content. It goes like this:

1. The point of lectures is to communicate information to a large group of people

2. The thing that lecturers want least is to communicate information to a large group of people

The difference between the two is what constitutes the 'group' - in 1, it's students, in 2, it's everybody. The only truly efficient (current) mechanism for identifying students is 'people who are physically in the room when I talk', which is basically not good enough because it doesn't accommodate the bits of the lecture that aren't talking - handouts, slides, reading lists.

When it comes to the handouts/slides/reading lists, there's no group identification mechanism, so the lecturer relies on making accessing the content really, really annoying. Physically picking up printed copies of notes at the door of the lecture theatre, for example.

Making access annoying is exactly the opposite of making access accessible.

This is not a surface level problem - it's in the roots. I'm not at all sure what can be done to fix it, but if it does get fixed, it will have to be in the roots too.

***************************************

I wrote this about accessibility, but following a quiet mull, I don't think this is an accessibility problem - or rather, I don't think it's *only* an accessibility problem. The VLE was supposed to sort the access-for-students-only problem out, but it hasn't - VLEs are still barely useable environments that most lecturers don't like or - worse - understand.

That's not good. That's bad.

Very, very tentatively, could I maybe suggest that maybe, just maybe, HE should just loosen up a little about IP?


Thursday, 9 December 2010

Irritant

You know when you're looking for something, or you just found something you were looking for, someone always says 'it's always in the last place you look'?

That's because once you've found what you're looking for, you stop looking.

Let's all never use that phrase again, shall we?


coda: I should point out that 30 hour journeys with 11 hour time differences make me irritable. Apologies.