Tuesday, 24 August 2010

Vroom vroom iPad!

Last week, my husband caved. I knew it was going to be one of us, but to be honest, I always thought it would be me.

He bought an iPad.

It became part of our day-to-day immediately - I love the sweet little thing (especially 'Plants vs Zombies'). It's so easy! So fast! So many cute little apps, look at them, they're adorable!

I was reminded of an analogy I thought of months ago, but didn't realise was true until now (because I was busy *talking* about iPads rather than *using them and learning about them properly*, naturally):
  • Desktop (and laptop) computers are like geared cars.
  • iPads (and their tablety kin) are like automatics.
Here's the thinking behind that:
  • Desktops give you more control, but they're harder to use
  • Tablets give you less control, but they're easier to use
I prefer PCs myself (stop laughing), and I'm quite happy to wander off into the more bewildering realms of 'My Computer' and tinker with what I find. Sometimes I mess things up terribly, and often I get confused. It's hard territory in there, and sometimes, when the task is boring or fiddly (installing new software for example) I'd really rather not. But I do have a huge amount of control - if I want to have a poke around the program files, I can.

With a tablet, you don't have to know much about anything to make them work, and nothing is boring or fiddly or a chore. It's all smooth. What you give up is the ability to wander around places like 'My Computer', because there isn't one - or at least, not one you can ever find to access.

I think, in a couple of years' time, the current (but starting to fade) idea that all computer users - from the highly skilled to the I-just-want-it-to-work types - should use the same machines will emerge as having been a bad call. The same machines that bewilder the less-skilled irritate the life out of the highly-skilled, so why should they be the same? No happy middle-ground has emerged (yes, pipe down Mac users) and the odds are good that that's because there isn't one. The two groups have different needs, why should they use the same machines?

We have different tools for different tasks for different users in almost all fields of life, and I can't see why computers should be any different - or how they've stayed different for so long.

And until the division becomes clearer, I'm just going to keep playing 'Plants vs. Zombies'.

Thursday, 19 August 2010

Explaining the structure of XML

I thought of a good way to explain the structure of XML to someone who hadn't seen it before today:

XML is like Russian dolls.



Each doll has two halves, just like each XML element has two tags.

Each doll needs both halves to match up to be complete.

The dolls have to match up in order - the littler ones must always go inside the bigger ones.


(NB. I haven't managed to stretch this out to schemas yet, but I'm working on it...)

Saturday, 14 August 2010

Inception: I think I've cracked it

Ok. I could be wrong, but I *think* I've worked out Inception. Which is to say - there is an answer, and this might just be it. Naturally, the following contains spoilers.

If you can prove me wrong, please do.


Here we go...

1. Cobb is dreaming for the entire movie.

2. Cobb is not the protagonist. Mal is.

3. Because we are watching Cobb's dream, we never actually meet Mal. This is a movie where we never meet the main character.

4. All the characters but Cobb - including Cobb's version of Mal - are dreamed by Cobb. All the things that happen are events dreamed by Cobb. Consequently - the entire movie is a McGuffin.

5. No, all of it. It's all a McGuffin.

6. It's a McGuffin because it's the story Cobb's unconscious has made up to protect itself. But one real thing did happen -

7. Cobb and Mal were indeed stuck in limbo together.

8. She got out.

9. He didn't - he's still there.

10. (Brace yourselves)

11. He didn't plant the suicide idea in her. She planted it in him. She did the inception.

11.5 Consider - on whose word do we have it that Cobb did the inception? Cobb's. We see them both reciting the lines about waiting for a train, but we never see anyone say it for the first time.

12. It didn't work.

13. Because inception doesn't work.

14. It's because Cobb's drive to be the protagonist was so strong that he couldn't accept the incepted idea, or with it, the truth that she was right the whole time, and that he was the one living in the not-real world. The story was made up by his subconscious as a way to protect him from the idea that he wasn't the protagonist.

15. That drive - to be the protagonist - was, in the story-pattern used by mainstream movies, masculine.

16. The movie was pulling an act of inception on you - planting the idea that the woman might be the agent, the protagonist. Female agents do not happen in our mainstream movies, our stories. The movie is a story about our stories and our stories are gendered. The story world were the men are always the protagonists, that is a not-real world. Those stories are not good for us. They're keeping us stuck in not-real thinking. We need better stories now.

17. It won't work.

18. Because inception doesn't work.

Thursday, 12 August 2010

Embedded learning materials

Here is an example of how common cartridge materials can embed in websites like blogs.


This quiz material (it's QTI 1.2, standards fans) is actually hosted on cloud.icodeon.com by the good people at Icodeon, who are the only folk who are making a non-VLE-dependent Common Cartridge player at the moment (if you know of another, please let me know!)

It's embedded here the same way that a youtube video embeds - the content isn't present on this site at all.

It looks pretty shmick, but the key point here is that the content isn't present on this site. Publishing people I know you've spotted this already - that means it can't be copied, which means in turn, it can't be pirated.

Sweet, eh?

(Common Cartridge is a new educational content packaging standard by IMS global. More about Common Cartridge can be found here.)

Friday, 14 May 2010

The Real Problem

I like problems. Fixing problems is fun, but working out *exactly* what the problem is is funner (and usually three quarters of fixing the problem, but I digress).

I've been thinking about that phrase, where people say 'the real problem is...' Increasingly, I think that's not a useful phrase. Consider this scenario - which is the 'real' problem?

1. My car is making a terrible noise

2. I might need to take the car for a service, but honestly, I'm just not sure

3. Why do things like this always happen to me?

Answer (in my opinion): They're all the real problem. They're all problems, and they're all real. But here's the kicker: None of them are actually solvable. None of them contain enough information to make itself solved. They contain enough information to identify what information might be needed to solve them, but they don't contain enough information in themselves.

So let's add real problem number four:

5. My car's timing belt is about to break

Now *that* is solvable. The solution is: Go to the mechanics and get the timing belt replaced. That will solve problems 1 and 2, but not 3, which is still a pretty good run. Point being -

The problem that has a possible solution is the real real problem.

(Unfortunately, 'I don't know enough about cars to realise that the timing belt needs to be replaced' is a real problem unto itself... but that's for another day.)

Monday, 10 May 2010

How to manage your reading list

I stumble across a million Interesting Things to read every single day. This terrific, but it's also problematic, because they do tend to get tangled up. Here are the problems my Interesting Things used to cause:

1. I would wind up with so many open tabs that I couldn't actually see what they are any more, creating a navigation problem.
2. I would get to the end of the day, close the browser, and poof! All that good and useful stuff would disappear, never to be found again.
3. It interrupted my workflow - I would take time to read an article about UX that could have been spent actually working on UX, just so I wouldn't lose it.


I've now worked out a process that has fixed these three problems. It uses two tools:

Instapaper is 'a simple tool to save webpages for reading later'.

Evernote is a souped-up bookmarking service, which lets you store pretty much anything you need to remember.


Here's the process:

1. Find an Interesting Thing to read
2. Add it to my instapaper account
3. When I have time to get some reading done, choose an Interesting Thing from my instapaper
4. Once I've read the Interesting thing, save it to my evernote account.


So - I always know what Interesting Things I have/haven't read, I can keep a tagged & searchable record of all the Interesting Things I've read, and I don't lose time trying to keep up with my Interesting Things when I have other things to do.

Commerce and tolerance: A lesson from Gothdom

This weekend we were in Goathshead, just outside Whitby, for a wedding.

Whitby is a great place. It's a beautiful harbour town in Yorkshire, full of ice cream stands and fish and chips shops. But it's not all sweetness, not by any means.

Have you ever read Dracula? Remember that bit where the boat sails into harbour and all the crew are dead? And a huge black dog (Dracula) leaps from the boat, and runs off up the cliffside to the ruined abbey looming above? That's Whitby. Bram Stoker wrote the whole book there. Which makes sleepy, pleasant Whitby a mecca for Goths.

There are goths everywhere, and goth-oriented shops on every corner. It's bizarre, and fascinating - how does this quiet little town feel about being colonised by these strange people with their eye-liner and Wiccan tendencies and big stompy boots?

A lady in a jewellery shop gave some insights. Apparently, the town gets along with the goths quite well. 'We do have some people who make trouble,' she said. 'But they're outsiders. Not Whitby people. Whitby people wouldn't do that.'

The goths have events, Bazaars, and festivals all year round. There is even - no joke - an annual football match, where the goths play the staff of the Whitby Gazette. The goths are good for business, too - usually they come into the jewellery shop looking for jet (no surprise there).

The worst problem she sees facing the goths? Weather. 'It is a shame when it rains - they do take ever so much care with their hair and makeup, you know.'

All this makes me think of the incredible power of contact. Put two people - or two groups of people - into contact, and they're almost invariably going to come to the conclusion that the other group are just people. That's because most people are just people.

One of the oldest and simplest forms of contact between different groups is trade. This is not a question of one person being falsely nice to another person from a group they don't like in order to take their money (although that does happen). It's more that it's almost impossible to define someone by their membership of a group when you're actually talking to them. And when trading, you have to talk.

'How much is that?'
'Ten pounds.'
'It's nice, isn't it?'
'Yes, I think so.'

Or:

'Can I have a serve of fish and chips and a tango please?'
'Sure.'

It might not seem like much, but cumulatively, little transactions like those can erode barriers between groups that would not otherwise come into contact at all. I like to think Whitby is a bit like that - a place where people who on the surface have little in common have had enough contact, at least part of it through trade, that everyone has basically become accustomed to everyone else. Like I said before, Whitby is a great place.

After I'd bought myself some nice jet earrings, we went back to Goathshead to see Kirsty and Sally get married. It was a beautiful wedding, and the staff at the hotel where the whole thing was held were just terrific.