So why is this a big deal to me?

Last weekend was the third OggCamp conference, OggCamp 11, at the Farnham Maltings in Surrey. Two years ago, at the first OggCamp (a one-day event at the Connaught Hotel in Wolverhampton), we invited Andy Stanford-Clark (@andysc) to be our opening keynote speaker. Andy co-invented the MQTT messaging protocol about 10 years earlier and, while there was a server implementation of MQTT (Really Small Message Broker; RSMB) that you could download for free from IBM’s website, it was proprietary and there was no open source implementation available.

Andy wrote a new presentation, especially for OggCamp, describing the geeky innards of his Twittering house (as seen earlier that year on the BBC). The presentation was a fantastic kickstart to the day and (somewhat predictably for a conference with its foundations firmly in the open source world) Andy was questioned about what bits of his home automation system were built on open source software and open standards. The one significant part of the system that was proprietary was RSMB (the core part that enabled all the parts of his house to communicate).

Then OggCamp started, we had a good time, and we went home exhausted but happy.

And then, just two weeks later, Roger announced that he’d registered a new project called Mosquitto (as in MosQuiTTo) on Launchpad. He’d been inspired by Andy’s talk at OggCamp to write an open source alternative to RSMB. Within what seemed like days he had a working bit of code which was taken up and tested by others in the open source community and hardware-hacking communities like Homecamp.

I cannot claim any credit at all for all the hard work that Roger and others put in developing and testing Mosquitto. I’ve always been proud, though, that Mosquitto was born at OggCamp – we played our small part in helping connect the previously mostly corporate/business MQTT with the open source communities.

That Facebook announced they were adopting MQTT for their new messaging system the day before OggCamp 11 meant we could vicariously revel in Roger’s glory while we tried to find out just whether Facebook had adopted his code or their own implementation. The answer seems to be somewhere between the two.

And while I’m proud for OggCamp (of course), I’m also excited for Roger in his own right that his name is now in the licence agreement of apps from the mighty Facebook – that kind of recognition for your hard work must be such an amazing feeling!

In the past…

Traditionally, you would probably publish papers about your idea in peer-reviewed academic journals so that people interested in that area would read about it and think “that’s a cool idea; I must adopt that approach too”. Similarly, you might present about it at conferences where your audience of like-minded people would listen and think “that’s a cool idea; I must adopt that approach too”. If you had teaching responsibilities, you likely also taught your students about your new approach, explaining the weaknesses of the old approach and why this new approach is better so that when they come to doing their own research projects they think “that’s a cool idea; I must adopt that approach too”.

Except (I’m guessing here) it probably doesn’t always work like that. Especially if your cool new research idea is a statistical method. Especially if your new statistical method requires its users to sit down with a calculator and manually work through an equation instead of just opening a data file and pressing some buttons in SPSS, the statistics package popular with psychologists, marketing people, and others.

The unfortunate upshot is that your cool new statistical approach just doesn’t really get off the ground, no one else writes about using it (so you don’t get the all-important citations in other people’s publications), and it just slides quietly away into the ether.

In the 21st C…

If you are as cool as your cool new research idea, you might also embrace the wonders of the world of social media and online communications. Obviously, publishing in peer-reviewed journals, presenting at conferences, and teaching your students are all good and necessary things to do. But they’re probably not enough in some cases–and I’d guess that statistical methods is probably one of those cases.

I don’t know whether Hayes & Preacher (or Preacher & Hayes) went through that exact thought process when thinking about how to promote their cool new statistical methods to psychologists and other social scientists, but it seems that usability was one of their aims (for example, Andrew Hayes suggests that people have tended to stick with the older methods, rather than adopt the newer and better methods, because the old ones are “simple and widely understood”; Hayes, 2009, p 411).

• Written macros to extend SPSS
  Users can use the macros to (fairly) easily run the tests using SPSS, an environment they’re already familiar with. Macros are a bit fiddly to work with so, for one of their tests, they’ve even written a custom dialog that you can install in SPSS which adds a new entry to the Analyze menu so that you can just open a standard-looking dialog box to select the appropriate variables names and run the test. All this is available for free download from their website.
• Created a Facebook group to answer questions
  You can start a new topic (thread) to ask a question or describe a problem, or you can browse the existing 1636 (and rapidly rising) topics (at least, I’ve been able to before but today it seems the back/forward links have gone walkabout). You can also use Google to search for specific topics. Both Preacher and Hayes typically respond to questions and problems within a day. When I was having some technical problems, they asked for a my data file and ran the test on their own machines to check whether it was just my installation of SPSS that was the problem (it was).

Benefits for users

As a student trying to understand the statistical procedures by reading and re-reading their journal papers multiple times, it was invaluable to be able to ask the authors themselves (via Facebook no less) to clarify specific details as they applied to my particular experimental design. Browsing the 1000+ topics of discussion was also very educational as I came across answers to questions that I hadn’t even thought to ask yet.

Benefits for them

The benefits for them are surely great too. Obviously they have to spend time writing, testing, and supporting their macros etc, and they also have to spend time responding to help requests on Facebook. In return, though, they vastly improve the ease of using their statistical procedures, while also giving you (the user) a warm and fuzzy feeling about the procedures (the power of positive affect) and that there are many other people out there trying to use the procedure too (the power of social norms), all in all making you (I would guess) more likely to keep trying and to talk about the procedures to others. Those are the intangible and difficult-to-measure benefits of a good user experience.

In addition, they’re getting loads and loads of feedback from their users on where their procedures or explanations are difficult to understand, or where users commonly have problems, so that when they write a book on it, they’ve got valuable material to respond to and include which should make the book incredibly useful to users. We’ll see if that’s true when their book, and accompanying new macro, comes out next year. And there’s another thing, while they’ve got you in a discussion on Facebook, it’s practical (but also good promotion) for them to refer you to one or other of their papers, or to mention the book coming out next year. And there’s a list of up-coming events at which they’ll be conducting workshops on these statistical procedures. It all helps to boost citations.

Everyone wins

I think it’s brilliant. Not just because they helped me by answering a question within a day and diagnosing the problems I was having running their macros. But because they’re tapping into resources that are free and much of their target audience already use. And by doing this, they’re making their cool ideas as accessible as possible, which can only really be a good thing for everyone concerned.

References

Hayes, A. (2009). Beyond Baron and Kenny: Statistical Mediation Analysis in the New Millennium. Communication Monographs, 76(4), 408-420. doi:10.1080/03637750903310360

Disclosure

I work for IBM, who own SPSS.

When I set up my blog, back in March 2006, I adorned its posts (and pages) with the RedStripes theme. Which was particularly exciting because, despite never having seen PHP previously, I managed to fix a bug in it!

The RedStripes theme was always slightly awkward because it didn’t resize very well (either if you changed the size of the font, if you used page titles that were too long, or if you just added too many pages). While also rather pretty, IMHO, it was also slightly dated (I like to think ‘retro’) in style, even at the time I adopted it.

So, having seen the bang-up-to-date artistry of Jono Bacon and Stuart Langridge’s blogs (basically the fact that they have natural curves that emulate the real world, rather than straight lines), I went looking for something similar.

Notepad Chaos was one of the first I found and no matter how many themes I found this one stuck out because, well, it doesn’t look like a WordPress blog.

So I spent another couple of evenings customising it slightly to fit the content on my blog, including creating the tag cloud pinned note, and tweaking meta information in the post footers, I give to you my new theme–unless you’re reading this on the blog rather than via RSS, aggregated, or on Facebook – which would make it all rather pointless!

P.S. Coincidentally, when I first applied the new theme to my blog so that I could see how it looked and how much customisation I’d have to do, @benjamindyer was searching for something, came across my blog in the search results, and tweeted his reaction and observation (though I can take no credit for the actual design)!

Rather nicely, after installation, it launched a wizard that stepped me through importing my bookmarks from my local Firefox file. They imported okay and were saved as private. I then did some spring-cleaning and deleted out-of-date bookmarks, then tagged and re-tagged others. The imported bookmarks were automatically tagged according to the bookmark folders they’d been in, which was helpful.

So, anyway, here are my delicious tags. If you click through a tag, you’ll see the bookmarks that I’ve classified with that tag.

Whenever my phone rings or I receive a message, the penguin starts to spin round and flash lights to let me know. In fact, he even starts to spin and flash before my phone even starts to ring! How clever is he?

Second, this is my funky gorillapod – a kind of tripod for my camera but, unlike traditional tripods, it doesn’t have to be set on a flat surface. In fact, it thrives on uneven surfaces…like the back of this chair.

Cool huh?

As you may notice, if you hover your mouse over the little icon at the end of the following link, the Snap Shots previews (formerly known as Snap Preview Anywhere) now works fine and dandy.

The nice Erik Wingren, head of UX Research at Snap.com, posted a comment in response to Saturday’s blog-post about how I couldn’t get Snap Shots working on my website. His comment prompted me to check that I had the latest and greatest version of the WordPress plugin (I didn’t) and to try it again. This time it kind of worked but not always.

So Erik posted another comment to say that my unique key was too short. He was right. I registered for a new key and now it works! I can only be impressed that it worked as much as it did with the abbreviated key!

Slightly sheepishly, I did check the old version of the plugin in case I’d always had the key wrong but I hadn’t – so I’ve no explanation why the old plugin didn’t work. But the new one does, which is the main thing. The WordPress plugin makes it incredibly easy to install (if you’re used to installing WordPress plugins) so I’m not sure what Snap.com could’ve done to make it more idiot-proof.

Good UX research from Snap.com, I think. What a great way to meet your users. I wish it were that straightforward to get feedback from users of business middleware….

p.s. Here’s some blurb that Snap.com provide to explain just what Snap Shots is about and how you can disable the previews if they drive you up the wall when you’re reading my blog (though I suspect that most people who read this use an RSS reader and probably have absolutely no idea what this entire post was about):

Introducing Snap Shots from Snap.com

I just installed a nice little tool on this site called Snap Shots that enhances links with visual previews of the destination site, interactive excerpts of Wikipedia articles, MySpace profiles, IMDb profiles and Amazon products, display inline videos, RSS, MP3s, photos, stock charts and more.

Sometimes Snap Shots bring you the information you need, without your having to leave the site, while other times it lets you “look ahead,” before deciding if you want to follow a link or not.

Should you decide this is not for you, just click the Options icon in the upper right corner of the Snap Shot and opt-out.

She talks to me, tells me the time, tells me the weather forecast, reads messages to me, flashes her lights in pretty colours, and waggles her ears.

My Mum has a bunny too. Her bunny has married my bunny (fortunately about 250 miles apart) so when my Mum moves the ears on her bunny, the ears on my bunny move the same way.

If we were really sorted (or geeky, if you like), we’d arrange some kind of code. So far, the only meaning we’ve established is that ears down last thing at night means ‘good night’.

But it’s all fun.

I’ve wanted to buy a laptop of my very own for about a year now but, already having a desktop PC that works fine, I couldn’t really justify it. Also, I wasn’t sure what I wanted from a laptop: a desktop replacement like the Dell Inspiron, which my brother bought last summer with a huge screen but large and heavy, or an ultraportable like the little Vaios and iBooks that might be a bit underspec and overpriced.

Then a couple of weeks ago I stopped procrastinating and decided that I want a small, light laptop that had to have a bit of umph and could run Linux. I had no idea what was available so I just looked at the main manufacturers like Dell (too big), Sony (too expensive and focusing a little too much on what it looks like over what happens under the lid), Apple (ditto Sony)…

In the past, Tony has bought new hardware based on recommendations in the PCW magazine Group Test reviews. So I did a search and discovered, conveniently, that PCW’s February 2007 issue did a Group Test of lightweight laptops. Their favourite, with a glowing review, was for the Samsung Q35. After looking at some of the others that they tested, I came to the same conclusion.

Then I discovered that the Q35 also comes in RED!!!

After a bit of debate about settling for the slightly lower spec Q35 Red over the standard silver Q35, I figured that what difference there might be between a 1.83 Ghz Intel core 2 duo (the red one) and a 2 Ghz Intel core 2 duo (the silver one) I’m unlikely to notice with my type of usage (email, Web, word processing). So I plumped for the Q35 Red.

And it’s so cool!

The keys on the keyboard feel really nice to type with. There’s is a slightly odd keyboard layout in that you have to use the Fn key to get Home and End but it actually takes less getting used to than I expected. What still catches me out is having to reach slightly further to the right for the right-hand Shift key. But even so, it’s all very nice. Another thing that user reviews pointed out as being negative is the slight stiffness of the touchpad buttons but it’s not a big deal and I tend to double-tap the touchpad anyway.

Other than that….the build feels really solid (including the DVD drive which doesn’t feel as flimsy when open as on some laptops), the monitor resolution (widescreen 1280 x 800) compensates for the smaller screen (12.1″), the picture quality is great, the battery life is good….

….and almost everything worked on Ubuntu Edgy out of the box!

I booted first into the factory-installed Windows XP Pro to check that all the hardware worked (like the SD/MMC etc card reader). After some initial confusion about which way up to insert an MMC card (the user manual says with the label down, but actually it’s with the label up), all was fine. So I wiped the harddrive and installed Ubuntu Edgy.

All the software comes on CDs in the box with a healthy understanding, on Samsung’s part, that users *might* want to reinstall at some point (even if it’s just because of a harddrive failure), rather than expecting a hidden partition on the harddrive to be sufficient. Actually, there is a hidden recovery partition on the Samsung Q35 but it contains some recovery software, rather than an entire operating system. The idea is that you can take an image of your machine at certain points to which you can revert in future if all goes wrong. I figure that if I’ve got all the software on CD and I screw up my machine *that* much, I’d rather just do a straight reinstallation. Besides, the recovery software runs on Windows.

So, in the BIOS, I made the hidden recovery partition deleteable and told Ubuntu to format the entire harddrive. Unfortunately, I think there’s a slight bug in the BIOS so that whenever you do a cold restart (ie shutdown and power off then power on again) the BIOS setting defaults back to protecting the hidden partition from being deleted again. And I kept forgetting to switch it back to being deleteable. So, on my second installation attempt, I remembered to make the hidden partition deleteable. Possibly predicatably, however, after installation, when I next powered on, the machine wouldn’t boot because the BIOS had reverted back to protecting (ie hiding) the recovery partition area of the harddrive. Which meant that the Master Boot Record (on the first bit of the harddrive) was hidden (which is not ideal).

In the end, I gave up and wrote off the few Gb of hidden partition area and installed into the rest of the drive. Strangely, the installation took ages this time. Still, it seems okay and I’m going to do a fresh installation of Ubuntu Feisty when it comes out in April anyway. Slightly annoying that I can’t use that area of the drive but my BIOS version is up-to-date – and I’d have to reinstall Windows to update it now anyway – so I’ll have to live with it.

One thing that I didn’t mention about the factory installation is that there’s another partition which contains a media centre (based on Windows XP) that you can boot into without loading the full operating system so that you can look at photos, play DVDS, and listen to music. There’s even a separate power button on the laptop for it. Because it’s all part of Windows XP I couldn’t keep it when I installed Ubuntu but, at some point, I’m going to investigate the possibility of installing something similar based on Linux and, hopefully, hooking it into the second power button. Apparently I know someone who knows about this sort of thing so there’s a chance that it might work too.

Anyway, on installation, Ubuntu automatically detected the correct screen resolution and just worked. To work on our WPA-encrypted wireless network, the wireless needs Network Manager installing with some slight configuration (though Feisty should do this better), and there’s a weird bug in the sound card support that requires you to run a command (see these instructions for installing Fedora on a Samsung Q35 for the command). Without the command, the sound works but there’s a high-pitched whistling sound that quickly gets irritating.

The touchpad works (including double-tapping to do a double-click) but vertical and horizontal scrolling using the touchpad doesn’t work out of the box. At some point I’ll look into that. I successfully burnt a CD using the Nautilus-integrated drag-and-drop method a couple of nights ago (easier than I remember it being on Windows) so that’s all fine. The card reader does work but ironically only seems to detect the DRM-protected SD card and not the DRM-free MMC card. Hopefully that will change with Feisty because I use an MMC card in my digital camera.

So, all in all, I’m a very happy bunny!

When I was looking for a new camera, one of the things that made me doubtful about getting a Canon is that they don’t mount as a harddrive when you connect them to the PC. When Tony first got his Canon PowerShot about four years ago, this meant that you had to install the Canon software onto any PC that you wanted to connect the camera to.

We did use a USB card reader to get around this but the card reader is bulky enough that it doesn’t always fit between the other connectors on the back of the computer. The advantage of the card reader is that it *does* mount as a harddrive. So you can just drag and drop the image files from the card to your PC. Which is nice and easy.

Four years on, though, Canon now supports PTP protocol which means that when you plug the camera into a PC, the operating system goes “Oh that’s a digital camera you just plugged in. Would you like to a) import photos from it, and b) do that every time?”. The camera isn’t technically mounted as a harddrive but your interaction with it is much the same as if it were (though I don’t think you can copy files from the PC back to the camera).

On investigation, the operating systems that are friendly enough to do this are Windows XP, Mac OS X, and…..Ubuntu 6.06 (Dapper). As luck would have it, the week I got my new camera was the same week that Ubuntu Dapper was (finally) released. So a quick-ish upgrade on my home PC later and….

…it couldn’t get much simpler: I plugged my camera into my PC with its USB lead, Ubuntu detected it and popped up a dialog asking if I wanted to import my photos. Good eh?

So now the one thing I had against Canon digital cameras is no more. And having played with my new camera quite a bit over the past month, I thoroughly recommend it to anyone else who might be looking. It’s small and sleek so it fits easily into my pocket (my major requirement); it takes pictures as good as or better than Tony’s older Canon PowerShot; the interface is fairly usable – not perfect but easy enough to get the hang of with a bit of playing around (for instance, getting used to the ‘FUNC. SET’ vs ‘MENU’ buttons); the battery charges quickly.

The downside is that even after you’ve paid out for the camera, you still really need to get a case for it (another £20-odd), a larger memory card (another £20-odd for a 1GB MMC card), and I find it useful to have a spare battery so that you can have one-on-and-one-on-charge (yet another £20-odd).

Still, I’m very impressed with it as a camera and am looking forward to many snappy times ahead.