Sunday, 29 September 2013

Sainsburys self-checkouts and lazy UI design

So, I know it's almost a cliche to complain about the self-checkout machines in supermarkets, but I generally find them incredibly efficient. I'm going to try and write this entire post (which won't be very long) without mentioning "unexpected items" at all. 

As I said, I usually find the process very efficient - at our local Tesco, it means one staff member can be serving about 15 customers at one time, and I very rarely have any major issues, although I guess I am younger and more tech-savvy than the average person, so it's possible there are some features that I just sort of take for granted which are in fact confusing. There's an interesting article at coding horror on this. However, there is one feature of the Sainsbury's version of this machine which I find extremely annoying. 

When you have scanned all your shopping, and pressed the button which takes you to the payment screen, if you insert your card into the card reader, you get this message.

As you can see, this message annoys me enough that i took a photograph of it. In case that's not legible, it says "Please press the card button". Now, I know for most people reading this it will be immediately obvious why this is terrible, so please excuse me while I rant for a moment:

The machine knows that I entered my card into the card reader. It knows that every time anyone ever enters their card into the card reader, they should have pressed the card button first. So why the hell doesn't it "press the card button" for me? 

I really only think of one plausible explanation - the way the person writing this software had implemented the "card button", it was much easier to put in this intermediate screen and have the user go back and physically press the button than it would have been to automate the process. I can think of no possible good reason. (I can actually think of one other bad reason to do this - it was somehow part of whatever specification the developers were working from that people had to explicitly push the card button to pay by card - but that just pushes the incompetence up a level). 

As evidence that there is no good reason, the machines at Tesco do display the sensible behaviour - if you insert your card once you'e gotten to the payment screen, they behave in exactly the same way as if you'd pressed the card button first. 

Now, assuming my laziness explanation is correct, this is really, really lazy. This is the sort of lazy that I probably wouldn't try to get away with if I were writing an Excel macro to be used by half a dozen people in my office. How on Earth did someone get away with it when writing software to be used by the general public, for one of the biggest retailers in the country? Perhaps the World is Mad after all (incidentally that is a reference to a future post that I haven't written yet, maybe it will work as some sort of commitment device...).

Thursday, 19 September 2013

The first 100 hours

So, I recently read The First 20 Hours, by Josh Kaufman. This books is very weird, in that it basically seems to consist of Josh Kaufman coming up with one pretty interesting idea, which can be written in about two sentences, or at most two paragraphs, and then trying to figure out a way to spin it out into an entire book.

The idea, basically, is that you will get surprisingly good at things surprisingly quickly if you just commit to practising them on a regular basis for a reasonable amount of time, and if this practice is sensibly directed. These ideas are amply summarised, along with several anecdotes, in the first 39 pages of the book, (which, incidentally, is in large type). In fact, the enormous majority of it is summarised in these 10 tips: 
  1. Choose a lovable project.
  2. Focus your energy on one skill at a time.
  3. Define your target performance level.
  4. Deconstruct the skill into subskills.
  5. Obtain critical tools.
  6. Eliminate barriers to practice.
  7. Make dedicated time for practice.
  8. Create fast feedback loops.
  9. Practice by the clock in short bursts.
  10. Emphasize quantity and speed
And yes, I agree, most of these are pretty obvious: I mean "obtain critical tools"? Here's me thinking I could learn to play the guitar with just a piece of string and some chewing gum...

The rest of the book is 5 examples of Kaufman applying his methods - he learns to play Go to a not-totally-terrible standard, buys a yoga mat (this is almost literally accurate - he "learns" yoga in a total of 3 hours practice, incidentally, his wife is a yoga instructor...). builds a simple website, learns to play the ukulele from scratch, and learns to windsurf.

Of these, the only one that is actually impressive is the ukulele - he goes form nothing to playing in front of a fairly large audience in literally a week which, while it is obviously possible when you stop to think about it, sounds exceedingly daunting the first time you hear it.

Anyway, pretty much the most important sentence in the book is one which I don't think is even in the book (I mostly skimmed it), but is certainly in his TEDx talk.
The major barrier to learning something new is not intellectual... it's emotional... feeling stupid doesn't feel good.
I'm not even entirely convinced that it's fear of feeling stupid. It's just easier to sit and watch TV than it is to pick up the guitar and play some terrible approximation of Au Clair de la Lune (because you haven't even started to learn tunes that you actually want to be able to know how to play), or try to figure out how to install an API so you can write your first Android app, or drop juggling balls all over the floor. I think the key idea in the book is that you should commit to spending 20 hours learning something (and admit that it's ok to be terrible at it for a good portion of those 20 hours), and just see how far that takes you.

So, anyway, I've decided to learn some new things. 20 hours a month is 40 minutes a day (which is conveniently just about the time I have left for myself if I come home in my lunch hour). I have decided to spend 100 hours over the next 6 months (allowing for the days when I don't get round to practising, etc) learning 5 new skills. I'll be keeping track of the time carefully (principles 7 and 9, I think).

I haven't yet decided what the 5 new skills are, but I think the first one will be playing the guitar. I bought a toy guitar from John Lewis a few months ago, and haven't played it at all because I can't tune it. When I recently got a new phone, on which the tuning apps actually work, it became much more appealing (obtain critical tools; remove barriers to practice). On the principle that generalists ship, and even though I'm very clearly in the dabbler phase right now. I'll try to record a video, or at least an audio recording of me playing something when I get to my 20 hours, and I'll post that, along with an update on what the next skill is going to be.

Friday, 13 September 2013

A return to blogging (for a while)

When I was in California a couple of years ago, Michael Vassar said something to me that pretty neatly summed up some vague thoughts I'd been having myself. Describing my existing blog (which has since gone on hiatus), he said that the majority of it was "like shooting fish in a barrel", and he's right. Most of my blog posts are about how crazy homeopathy is (shocking!) or how some immigration is probably a good idea, or nuclear power just isn't that dangerous. Now, some of these ideas might be part of the correct contrarian cluster, but most of them aren't even that - certainly not among the people I usually mix with. Most of them are part of the correct non-contrarian cluster. Pretty much everyone I know would agree with pretty much everything I've ever written on this blog. I've no idea if I should consider that a bad thing. I've been considering starting writing posts regularly again for a while, and haven't for three main reasons. One of them is that I expect that for a while, the posts would end up being navel-gazing rambles about why I haven't been blogging for a while*.  The second is that I was looking for work in relatively mundane professions, so was being fairly careful about my web presence. I'm now pretty settled in in my current job, and hopefully next time I'm looking for work, it will be somewhere where an interesting web presence is a bonus, rather than a hindrance. The third is that I'm just not sure that I'm right about as many things as I was sure about even two years ago, and I'm even less sure that the things I'm sure I'm right about are the areas where my ideas are interesting/entertaining/important. A few of the posts I'll write over the coming weeks will touch on this theme, but don't worry, I'm sure there'll still be some shooting of fish a barrel.

Anyway, to avoid this turning into a seriously long rambling introspection, I'm going to stop there, and commit (semi) publicly to writing at least one blog post a week until the end of the year. Hopefully at least one or two people still check in here every now and then, and if I do manage to keep up one a week, I'll probably start telling people about some of them. Also, bizarrely, I've still been getting 15+ hits a day even though I haven't been writing anything for about two years - Google is powerful!

* On this note, and to avoid saying it elsewhere - I was genuinely surprised by the number of people who noticed when I stopped posting a couple of years ago - come on people, how do I know you're reading this if you don't tell me until I stop writing it?