I was at a very interesting meetup (Cambridge Internet of Things) yesterday.
Alongside a thought-provoking presentation about online privacy and cloud computing, I learnt about the Physical Web project.
Scott Jenson explained the aims and the activities that are well underway. I’m a geek, I get excited by such things and my mind runs ahead.
As I watched people holding up smartphones to capture the projected slides, presumably to grab details, it occurred to me that giving a presentation might be a great physical web use case.
When you’re building something made of software (!), it’s widely-accepted best practice to write tests for it. Nothing new there. Attending an excellent event in Cambridge last week, a superb presentation by Tim Perry from Softwire made me realise something else though.
Writing tests makes your application more secure. This sounds trivial, but I mean tests like “does the widget do what it’s supposed to do” tests, not “does the app refuse log in if the password is wrong”.
I thought I’d write up something I did at work today, in case it’s useful to other “webmasters”.
We have a site which, through evolution, history and multiple editors, has ended up with a cluttered URL space. It happens.
This is a worthwhile thing to do for tidiness, to enable future redesigns, and to ensure good navigation (and hence Googlability). I was keen to do it in a way that maintained existing links, and in a way which would preserve search engines' knowledge of our pages.