My wife’s parents came to stay with us for a spell (Sorry about that I’ve been watching Firefly), and when they visit we often go out and about. It’s great when they come to visit because I wind up doing things I wouldn’t think to do on my own. On this outing Ed and I paid a visit to the Australian Maritime Museum.
I went to the museum for the Windows 7 launch a few days earlier, but I didn’t explore the museum itself. I just went in for the event and left afterwards, but took note that this was probably something Ed would enjoy (he is a history buff).
We went back over the weekend, and scored a few “big ticket” passes. The big ticket passes let us on board all the ships they have on display – HMAS Onslow (1968), HMAS Vampire (1959), The James Craig (1874), and The HMB Endeavor (1768). (If you have the chance, I recommend a visit.)
Does this have anything to do with software?
I was astounded by the craftsmanship, and amazing hackery that went in to these ships. Not just the ships, but everything from the sinks to the bookshelves to the plate racks. Additionally, the scale of these projects and the building upon of past knowledge was humbling. I also realised that, in general, to do great, large scale things requires great wealth – and apparently a cat of nine tails.
Standing on one of those ships and looking at the dual purpose… everything… was amazing. Everything was thought out. Everything had a purpose. Nothing appeared to be thrown in at the last minute on a whim. If something was done wrong, everyone on board could die. The shear magnitude of these projects, the number of people involved and the cross disciple input it would take to build – let alone invent – one of these ships was simply amazing.
The ones that really got me where the old ones. The 1768 wooden hull ship – the HMB Endeavor – was spectacular. This ship was built with things that mostly don’t exist, navigated with devices that are obsolete and using math that isn’t likely taught anymore.
This is an example of true engineering and hackery. A thing of beauty. And when the power goes out – it still works.
However software and computers are quite new. Designing and building system is often rushed, and the process is not respected. “Do it cheaper, do it faster” is the motto. Quality, for budgetary reasons, is an often an after thought. Yet I can’t help but think we are the ones at the beginning. We are the pre 1768 Endeavors. I wonder if these ships were designed and built with the “do it faster do it cheaper” mentality.
Ships were used to discover new lands and new routes, and software is used to discover new knowledge, understanding, human potential – and, yeah, twitter.
No one will die if web software goes bad, but it will never be as pretty or stable as a tall ship until the process is given a healthy dose of respect – and probably a few hundred years of trial and error.
All pointless rambling aside, if you get a chance, go outside to a museum. There is an amazing amount of unexpected inspiration.