Skip to main content

IET Mars Rover Lecture

On Wednesday me and my faithful sidekick Adam went to the IET Annual Prestige Lecture.
To cut a long story short I have prepared the evening in the form of a flow chart. I think it more clearly sums up the evening......

After looking into the facts I realised this night was possibly less about the IET Mars
Rover lecture and more about going to the pub. However, I couldn't be sure on this fact and would have to analyse the evidence further by a second trip into town to see the IET Mars Rover Lecture. As the lecture is an annual event I shall perhaps put it on the back burner.

Ah the lecture. Held at the Royal theatre (the well known bastion for the Notts intelligentsia), there was a fairly dissapointing turnout really.The hall was only about 1/2 full and 3/4 of that 1/2 were old boys in smoking jackets. I didn't let that bother me particularly, nor the fact that I had forgotten my glasses and that me and Adam were sharing his when important slides came up (a ridiculous accomodation because I can barely see through his). What did bother me was the speaker. The poor devil clearly had the jitters at speaking to so many people. It perhaps sounds cruel but what do I care? What's more cruel is having to sit through 2 hours of mad bumbling and sputtering. I hid in the toilet for half an hour in the middle of it and Adam informs me he tried to sleep but couldn't.

It's strange. Robotics is my life but this one man and his mad mumbo jumbo almost put me off it for life!

The only saving grace was the amount of up close and personal pictures I got of the Mars Rover. I was quite surprised how many open wires were on the Rover and why weren't they run through the Steel Chassis. I decided to assume it was the show model and not the final model as it also had a Wifi adapter sitting on the top of it. I like the eyes of the Rover which looked very like Johnny 5 from Short Circuit. It was strange really, there wasn't any security and the Rover wasn't behind glass and I was the only one there so I got to touch it and take some photos with it. I am expecting Robo Babies any time now.

This was a video of the robot. Taken on my phone. Not the best quality sadly :-(


Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second