My techy new year’s resolutions

A new year has started, a fresh 366 days (only 357 shopping days left till Christmas folks!) and so I want to share my techy resolutions for the coming year:

1. Get up to speed with unit testing for all platforms

I’ve been behind the curve on unit testing for a while now and I’m aware that I really need to put some time into working into my daily development cycle. I’m not talking about becoming a TDD zealot but I do understand the need for unit testing in producing consistently high quality code and this will be the year I actually get off my butt and do something about it!

2. (Re) embrace the Pomodoro Technique 

This year I plan to really embrace the Pomodoro Technique for at least 3 days out of 5. I’ve found it to be an amazing way to keep focussed and there’s really no excuse for not using it more often.

3. Get my JavaScript up to speed both on the client and the server

I’m still not entirely sold on the evented approach used by Node.js but I’m definitely planning to get my JavaScript up to a new level. Looking at what’s continuing to happen in the JS world I would be foolish to not devote significant time to a very exciting and ubiquitous technology … and whilst jQuery will do a lot good JS development will hopefully serve me in good stead.

4. Release at least one mobile app 

For Android of course but I’m definitely going to push out at least one app. Who knows – it could make me a millionaire by this time next year ;)

5. Finish some of the cool ideas I have kicking around

Like any developer I have a load of projects on the go and I really want to use 2012 to get some of them out of my brain and into the world. 

6. Contribute to at least one open source project

My open source contributions have dropped off lately and I’m hoping that I can find a project I can contribute to (suggestions welcome) … or maybe one of my ideas that can start a whole new project!

So that’s me – how about you lot? Got anything groovy planned for 2012?

 

Why HTML5 isn’t a replacement for Flash (and isn’t likely to be any time soon)

In some ways the content of this post is related to the recent Flash / Mobile snafu. Specifically because Adobe have made a big point of throwing their weight behind HTML5 in place of Flash on mobile platforms. This post is derived in part from personal experience and in part from a lively (and occasionally heated) debate with a colleague. In short it deals with my concerns over the dropping Flash support in favour of HTML5 and the common perception that anything Flash can do HTML5 can do (better).

Continue reading

Adobe’s killing of mobile Flash – a CF developers take

Firstly I’d like to make clear that I am in no way affiliated with Adobe either in the Flash or CF sense – I am a user of both products and, like so many others, work for a company who has based its business on the Adobe development stack.

I have no idea what prompted Adobe’s rather rapid dumping of Flash on mobile devices but the immediate impact on me and my employers should be minimal. That said, I wanted to take a look at how Adobe managed this announcement and the wider impact it could have on the community.

Continue reading