Sunday 29 March 2015

The Cake

I don't do a lot of cooking. So it was quite a surprise when a friend commissioned me to produce their wedding cake. In a strange way I should have seen it coming.

To cut a long story short, the cake is not made of eggs butter and flour. It's made of Lego. And the first question everyone asks is "how long did it take you to make it?"

The bride gave me 15 months notice to make the cake. The actual building didn't take very long. It was the planning that took the time. Planning what it was going to look like. Researching what real wedding cakes look like. Finding out the right sizes of each tier so they look right. And working out how to make circular things with square bricks.

The end result was an amazing success. The bride and groom were very happy with it. From a distance it looked like an ordinary cake. but everyone wanted a closer look, and everyone was taking photos.

There are various ways of making round things out of square bricks. The bottom tier uses a "traditional" method, like "steps" on their side. Most of the models and giant statues at Legoland use this method. I used the Paint program on my PC to draw circles of various sizes, and zoomed in to get a blocky circle on the screen, showing me where the bricks should go relative to each other. Then I experimented to see which size circle looked right. I created a number of quarter-circles in various radii to work out how thick to make the side of the cake (it is actually hollow, but needs a certain thickness so it doesn't fall apart when you pick it up). This also helped me calculate how many more bricks I needed to buy.

The top tier uses a different method of construction. By alternating the 1x3 bricks and the round bricks, it is possible to create a wall which can be curved. It looks a bit like the Colosseum. My first attempts were very multi-coloured, but this also helped me work out how many more bricks I needed to buy.

The middle tier uses another technique again. The method of construction relies on a special Lego part that was used in a Star Wars set from 2003 and some Lego Technic parts.

This construction method has the studs arranged horizontally around the edge of the cake. This tier is made up of 40 "slices" internally held in place by Technic pins slotted into the wheel, and held in tension externally against the neighbouring slice. The last slice was rather difficult to get into place... especially as I had to rebuild it several times. I didn't have enough white 2x12 plates initially. Although the first attempt helped me work out how many more bricks I needed, I miscounted, and had to order some more with only a few weeks to go before the wedding. The overall effect is very different from the other two slices, because it creates a much smoother circumference. This tier of the cake is also surprisingly heavy.

The cake has a feature not seen on most wedding cakes - a garage door. Remember I said that the cake is hollow? Inside the bottom tier of the cake is a lorry (the bride has an HGV licence). The door mechanism was quite a challenge. It uses slotted bricks as guideways for the bottom and top of the door to follow. After much experimentation, I found it was necessary to have separate guideways for the bottom and the top of the doors. It's a bit fragile, and needed repairing several times on the day of the wedding, but it was a great success.

On the lorry's flatbed trailer are two slices of cake. I take absolutely no credit for this fourth cake design. These come from the genius of Chris McVeigh, who produces all kinds of other amazing things in Lego.

The lorry also helped us resolve a practical matter on the day of the wedding: how are the bride and groom going to cut the cake? About three weeks before the big day, I realised we also needed a knife...

Please leave comments below if you want me to go into more detail. For the record, the wedding was in March 2015, in England.

(This post also appears on my personal blog). 

Wednesday 4 March 2015

on Data

Data has always fascinated me. Not so much the actual names, numbers and dates - but the bigger picture of data. What are we storing (personal data, chatter, garbage?) Why are we keeping this information, and what do we intend to do with it?  The purpose of this blog is my attempt at getting these matters out my head and into the open for discussion.

A few years ago, I heard rumours that Amazon was working on a way of suggesting the perfect gift for your girlfriend. based on the information that Amazon held about you, her, and what you both liked. Different versions of the rumour also suggested that Amazon would automatically purchase the said item for you, avoiding the embarrassment of you forgetting her birthday. I haven't been able to find the rumours online, but it would appear that Amazon have a Facebook app to leverage the vast power of relationships defined that other platform.

It would appear from the same article that Facebook are also trying to do the same thing: leverage the vast amounts of data in their social media database in order to make money. And every other company who has ever heard about the Internet is also trying to jump on this bandwagon: "Big Data" is a fashionable thing at the moment. There is a theory  that, if you have enough data, and you know how to analyse it, you can use this information to commercial advantage. The really big players in this arena are Amazon (see above) and Google (whose aims seem altruistic , but they make wodges of cash by putting relevant adverts in front of us). Other big and small names are trying to do the same thing, and commentators  are  divided about  whether the investment will pay off.

Behind the "Big Data" question is another matter, that I don't think is been properly addressed. "What do we want to get out of our data?" De Facto, different groups will have different agendas. The big online merchants want to use our data (who we are, what we are interested in, and most important of all how we relate to other people) to get us to buy things. In return for shiny gadgets (including, ironically, my ability to blog, by the way), these trustworthy corporate multinational companies have persuaded us to upload for free information about us which can be marketed.

The NSA scandal (via Edward Snowden) has revealed that Governments are using data that we assumed was safely locked away to spy on people, in order to protect us. Do I want governments to have a master key to my home, and to search through my stuff whenever they please? The truth is that it isn't only governments who can do this: our emails, social media messages, purchasing history no longer belong to us.

Returning to the point, what DO we want to get out of our data? Can we use data in a positive way? Have we already signed over any rights to keep our data private? And if it is private, is it any use?

On the other hand, there is information out there which is freely available - for example the vast Wikipedia, which has been shown to have a level of accuracy like the mighty Britannica -  but we aren't benefiting from it. People are more interested in stalking celebrities (who have plenty of airtime to teach nonsense) or watching videos of cats, than discovering the world in which they actually live. The child of a friend of mine left school this year, and is asking questions like " Did the moon just move in the sky", and "I thought Amsterdam was in Leeds" - a disastrous question for someone interested in traveling the world.  (if you don't know where Amsterdam or Leeds are, here is a map)

So we have this dilemma - data that we would rather keep private is of great value to companies who want our money - or if we have something to hide, it may be that Governments  are justified in spying on us in the national interest. This is the subject of much debate.  Yet at the other end of the spectrum, data that is public and readily available is not being absorbed by the masses to make us "better people" (whatever that means), or to better our society.

I firmly believe in the creativity of humankind to resolve problems. With my Aspy Mr Spock pointy ears on, there must logically be a simple solution to this dilemma, and others that face us in the world of data, and to the related issues they raise: how can we best use this data; and how do we appropriately control all the technical and social issues that surround them ? I don't have the answers, but collectively we can - and we will - come up with a solution.