Skip to main content

So busy

Ugh finished one course but am still currently engaged in another course. It's called a UCPD (university certificate in professional development) through De Montfort Uni. The place where they do the training is called the Axis Centre in Beeston Nottingham. They offer quite a few different courses and if you do a certain amount of them it adds up to this UCPD.

The reason why I am doing this UCPD is that I have decided to make an effort to to some continuing professional development every summer. Not to mention it means I get one day off work per week for a while :-)

I did an MCP course there a couple of years ago and they are very professional and know thier stuff. One thing I find really annoying is the complete and utter lack of reasonable priced professional courses in the Nottinghamshire area that people can attend to develop thier skills in IT.

I am not talking about doing an A-Level or even at HNC/HND level, but short courses that are aimed at professionals trying to develop thier skills. Castle College do a couple of community evening classes on Dreamweaver but I recently found at they are still advocating the arcance use of tables for layout of sites ect.. Whilst this is ok for people in the community it's not really good enough for people in business.

It got me thinking that I might do a basic teaching qualification such as the City and Guild 7303 and then try and do some part time teaching in the evenings if I can. Who knows. I am not sure yet even if there is anyone interested in it but I think I would like to find out.

The other thing I think would be good is to go round schools and do a workshop, something like 'Coding is Cool'. Try and get some young people into programming and not just wanting to study Media Studies (argh!!). I thought I could demonstrate some of the cools things you can do by using an example out of this book or something like it anyway.

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