A nod to Tales from a Trading Desk where I first discovered the article.

I thought it worth explaining the reason why I have released it under the Ordinary GPL and not the Lesser version. Firstly, I doubt this framework is ever likely to appear as part of a software release bundle - it’s more likely to be used to support the software development process and releases themselves, as opposed to actually being part of an application. And secondly, I would rather this were not used for direct commercial gain but to give users of freeware a benefit over commercial applications or software houses. There’s a very good explanation of the pros and cons on the GNU site.

It has some very useful articles on software architects and what they should be doing, as well as not doing! The most helpful for me personally was an article describing the role profile as I have worked with several architects over the years, and their daily duties varied markedly. As well as self-assessment, I think the published matrix could also be very useful whilst interviewing candidates - the author has attempted to assign a degree of responsibility to each aspect. For me, it’s not always cut and dried exactly who is contributing what to a particular project, be it a senior developer or an architect - it depends very much upon an individual’s desire to contribute as well as their particular skill-set.

In general, I was very impressed with the tone of coding the architecture. It is very hands-on and pragmatic in it’s approach, and dispenses with most of the fluff you sometimes hear from senior guys who haven’t got their hands dirty in a while. From my own experience and the way I have tried to build my own career, I’m of the firm belief that an architect who loses touch with the code base is asking for a fall…

What has this to do with cloud computing? Well, if the current trend for ‘Software as a service’ really delivers, then which browser you are using is going to be much more important than it currently is - the really interesting part of this for me as a developer is that Google appear to have made each tab run as a separate process. But re-engineering the tab processes is something existing market players could resolve with their own browsers should the need arise - with some difficulty, yes, but definitely within the realms of possibility for gifted software engineering teams.

Initial reports on Chrome don’t seem all that favourable, and it really doesn’t appear to contain the ‘killer app‘ which might make those outside the technology industry adopt it. I would wager that Google have a very valid reason for bringing a new browser to the market, and I can’t believe that making the JavaScript engine 10% faster is what it’s really all about. But at the end of the day, Chrome is totally dependant on whichever OS it’s being run on and suggestions that Google is targeting Windows as opposed to IE are way wide of the mark for the moment.

With thanks to El Reg, who made me reconsider my initial post.

It is still early days though, so please bear with me whilst I start to build it out.

In the meantime, one of the reasons I enjoy being a techie…

mauve database