Skip to main content

Arduino Sunday MkII

I went to the Arduino day at Nottingham Hackspace on Sunday again. Generally it was more of the same although I probably got a little more out of it this time as there was less time spent being confused. It was a chance to give the netbook (Dell Netbook) a good run for its' money and it did pretty well. I am beginning to more and more annoyed with the ubuntu netbook remix however. Its' inability to use the built in 3g model is annoying, there a several weird bugs in it and it occasionally freaked out whilst just trying open a menu. On the plus side, the size of the laptop is such a boon it makes it all worth while. I wouldn't relish having to lug my other laptop (Dell Inspiron 6000) about.?

The day was good. I didn't see many new projects from the last time but some brilliant progress has been made on the hackspace itself, with some interesting chairs from a cinema, some good desk spaces and some other additions. One of the founders Dominic (indeed another Dom!), was looking for new members. I must say I am always tempted. The rule is that you pay however much you think you should pay but just don't take this piss. It's hard to know how much I would actually go down to the place though as my time is so so limited anyway. It's something I will continue to think about. Once my course is over for this semester I may consider it. I might even consider it just as a place to go and study in peace and quiet.?

Anyway, the pics from Sunday are worth checking out.....

Comments

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