A blog about where emerging technologies meet access and interpretation for libraries and museums.
Tuesday, 8 February 2011
Luttrell Psalter - the Movie - For Free!
Monday, 7 February 2011
Lessons from Latte

Tuesday, 1 February 2011
Making Meaning

Thursday, 27 January 2011
Future History

For Christmas this year I got a great book called Lost London, published by English Heritage. It documents in photographs London in the years 1870 to 1940. The London that the combined might of planners, developers and the Luftwaffe swept away.
I have also spent quite a lot of time, for one reason or another in Streetview, looking around various locations. I even invented a game at home for my kids. I dump them somewhere in Streetview and they have to work out where they are (the best was the Isle of Mull - "Balamory!", the easiest "Grandma's house!")
So what technology has brought us is perfect recall. The tantalising and fragmentary glimpses we see of London 100 years ago or more give us an elliptical glance at the way life was, but the record is incomplete. Streetview allows us to stroll around towns cities and the countryside at will, observing every detail of architecture, town planning, fashion, advertising, automotive design, agriculture and even economic activity.
Which presents posterity with an amazing opportunity. If Google's slightly creepy Streetview vans take a snapshot of our country every 5 years, the legacy for future historians will be immense.
And it doesn't stop there. Mix in the petabytes of social media data generated around people and places that has all ben time-stamped, and future historians will have a field day. Imagine the young Charles Darwin was on Facebook while at Cambridge, or tweeting away his early cogitations. What insight we would have into his world and the way he came to think the way he did, and who might have influenced him. Stepping back into Streeview, Cambridge 1829, we'd be able to walk the streets as he saw them.
Which means, I guess, be careful what you write, wherever you write it. You never know how you might get entangled in future history.
Monday, 15 November 2010
Lowering The Price of Failure
Back in the 60s my mum was a secretary. She spoke a few languages and worked in some cool places, and she used a typewriter. When my sister was born, she gave up work and spent the 70s doing a fair imitation of the Good Life mixed with Abigails Party (think black forest gateau served with home-made wine…).
When we'd all decamped to college she wanted to go back to work, and picked up her typing again. Initially bamboozled by word processing, she was amazed with spellchecking and backspace. Make a typo - no problem: just lean on that left arrow button and hit "Del". No more tippex or white ribbons fed into clackety typewriters.

When Henri Cartier Bresson took photographs in the 30s, he would compose a shot, check the exposure, choose the moment, and press the shutter. Then he'd walk away - the shot done, the moment captured. I read on a blog yesterday about a guy who has an ambition to get 10,000 photos on his Flickr account by Christmas. And he's not even a photographer.
So the thing that has changed is that the price of failure has just dropped.
We're starting out on building a pretty ambitious bit of software. I've been agonising over features and what to include, but the great news is that we don't have one shot. For example, Flickr and Wordpress put out multiple versions of their sites every day. Matt Mullenweg (Wordpress) blogs about this here. If a new feature, or some "optimised" code doesn't work, they just revert back. The price of failure is low.
The price of building software and not iterating it can be very high.
Tuesday, 19 October 2010
Back to the Future
Monday, 20 September 2010
The Practice of Work
37 signals are one of my favourite companies. We've used Basecamp for a while, and I like their products, but it's the way they run the company that has always resonated with me.
So this interview with their lead dev was fascinating and contains some business practices that I've adopted (either knowingly or unwittingly) over the years.
Here are some:
- work from home on Friday. I take my kids to school, have a coffee with my wife and then dive in to my emails. 37 Signals go further. In the summer the office closes on Fridays.
- small is beautiful. A friend of mine started a web agency and, for some reason, he thought employing 60 people would be good. So he did. Then it went badly wrong, and 60 people lost their jobs. More people also means more personnel issues, bigger overheads and more management tiers.
- niche thyself (borrowed from Guy Kawasaki). If you're going to be small, find a niche and become the best. As a generalist you have very little ground to defend in any competitive situation.
- enjoy your work. I blogged on this before, but if you don't feel what you do matters, you won't do it well.
- employ smart people. When 37 Signals didn't like the available tools for building websites, they wrote their own. That's now Ruby on Rails. We had no code to convert conventional 3D models to XAML, so we wrote some convertors and built Turning the Pages.
- get code out the door. Then iterate.
- trust your employees. The 18 employees at 37 Signals are spread over 3 countries. The management (such as it is) trusts the people - they're in it together.
If you work for someone else, you might be sighing wistfully and bemoaning the culture you've inherited. If you control the culture however, then you can change it.