Ignatia Webs blog post – the future of mobile learning
I was very pleased to see this positive blog post review of a chapter I recently published in an open access book on mobile learning, which the blogger, Inge De Ward, also tweeted. Inge’s blog and Twitter feed must be quite popular, judging by the large number re-tweets that ensued. Please take a look at the blog post, and also the article (the blog contains a link to it)
I’ve posted before about passwords, specifically about the large number of extremely weak passwords revealed by the Adobe hackers. I recently saw a story on the BBC web site about a password that the security forces couldn’t crack. Here’s the article:
Man jailed for refusing to give police USB stick password
The password was $ur4ht4ub4h8, apparently a play on words relating to a chapter of the Koran. Next time some piece of software insists your password must include a mix of upper and lower case letters you can tell it to go take a hike.
If the password was so uncrackable, you may wonder, how come it’s in the article? Well as usual the security of your password is only part of the story, the authorities have many ways of extorting your passwords out of you, as this article describes:
David Miranda feels ‘invaded’ after password disclosure
The moral of the story, if there is one, might be that however secure your data is, you yourself are more easily hacked.
I’ve recently been interested to see a couple of examples where the concepts of test driven development and regression testing were clearly not applied, or at least not applied as they should have been.
The first example was FaceTime on my old iPod Touch. Having worked perfectly happily for years, communicating with an identical device in the UK, it suddenly started failing, and for a while I was reduced to using the much flakier Skype. As you do, I stared surfing the web for answers to the problem. I soon found a growing number of people interacting on various on-line forums complaining about a similar issue. Clearly, the common denominator seemed to be a regression caused by a recent upgrade to the iOS operating system on iPod Touch 4th generation. Interestingly, the response from Apple, if the experiences of those on the forums were anything to go by, seemed to be one of total disinterest. However, a few weeks later, Apple quietly released the following fix for a problem that had affected ‘some users’ (i.e. many):
http://support.apple.com/kb/DL1701
Now I know, from painful experience, how hard it is to test for this type of fault, but Apple should have had regression tests in place for changes that might affect popular standard apps like FaceTime.
The other interesting example was this one, about LG televisions sending personal data back to the company, even when a privacy setting had been turned on:
http://doctorbeet.blogspot.co.uk/2013/11/lg-smart-tvs-logging-usb-filenames-and.html
Now you would expect, if this software had been test driven, that a test would have been written that ensured that activating the privacy setting meant that data could not be sent. Instead, data was still sent, along with an indication that the privacy setting was turned on. Either that wasn’t tested at all, or it was driven by a stupid test. The alternative interpretation, that LG wants your data whether you like it or not is, I’m sure, not the case.
These two examples are instructive because they emphasize how important it is to (a) drive your designs with unit tests and (b) avoid the entropy of your software with regression tests.