Skip to main content

Course updates

Overview
If you know me then you will know I am a big fan of doing courses. I never stop! The latest in my summer of CPD is the Emarketing course from Axis Centre in Nottingham through De Montfort Uni. It forms part of the UCPD I have been studying towards over the summer. I have started it today and it is one day per week until the end of July.

On another note, I have been looking at what course I was going to do next year in September. I currently have a HND in Computing but have found it almost impossible to do the Top Up to the Bsc (Hons) in the evening. It's really annoying. The universities sometimes have no idea about the needs of people working in business. Anyway, the reason I wanted to do the top up was so I could finally get on to my long awaited Masters course in Artificial Intelligence. Just on the off chance after someone at work suggested it to me, I applied directly to do the Masters at DMU and sent along my CV ect.. I got an email back last Friday saying they felt I would be very suitable for the course so I am really really pleased! I hopefully start that in September (providing I get all the official paperwork sorted out in time). I will begin work on Skynet 2.0 immediately!!!!!

Emarketing Course
As said I started this today. First impressions are that it will be really good. The training was delivered in a fast to the point and punchy style that I like and not in an airy fairy academic way that lacks any really content. It looks like a lot of the course will be about promoting yourself using the social media and trying to harness your customers to collaborate on the content of your site. The message they are getting across really is the one I like and is very relevant. My only concern is I am not sure yet how we can apply it to our business. One thing I though about today was that our own internal project management tool has better features and looks better than our outward facing website. Crazy I know! I also had the embarrassing thing of where people asked to look at our site and as our site is so fat and full of crazy things, it took about an hour to load up and even then appeared very buggy on the screen. Not cool! As many of the people on these courses are crying out for development people and our company could easily clean up with them. God! We have got to fix it quick.

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