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

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

NESTA - Next Gen.

via Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt