Alan Coleman's

2008s project at work will be the next step in our re branding exercise, the development of an in house application to manage our content, otherwise known as a CMS. The technology will come courtesy of Microsoft’s .NET framework, that being a logical progression from the classic ASP (Visual Basic) set up used to create the web site and Intranet.

It is an exiting, if terrifying prospect, one that threatens a complete immersion in a whole new area of uncharted technology. However there is hope, already the human logic of those that developed this framework has started to show itself as little different from those from the open source sector. For instance, I felt almost at home with the concept of Microsoft’s Data Tier Components, and begrudgingly acknowledged that someone has probably put a great deal of thought into what I’ve always known as, Layer Separation.

This is only the beginning of a momentous project, but what is clear already is that the .NET Framework is not quite the bloated WYSIWYG editor that people like me used to say it was.

What’s this, Something positive about Microsoft?

Maybe, only time will tell.

When I first built my website things where different, the web was still very much a media to look at and navigate, rather than to interact with like it is now. Initially I hand built HTML pages to show my photos and organised the various albums into a file structure, to save on server space and download times I compressed all the images down to 30k. Laughable when you think about what we can do now, but it served a purpose. They were my photos on my website and I thought that was a million miles away from having them sit in dusty Truprint envelopes under the bed.

From flat pages I moved to an open source CMS, Plogger, that I hosted and adapted to my own needs, and whilst it wasn’t great it made the process of publishing photos less painfull. But as with most things in life, the novelty wears off. As much as one would like to, there isn’t time to get stuck in and develop functionality and improved scripting because there’s too much of that to do at work. When this happens things don’t get used and stagnate, it becomes a corner of the web that sits redundant. I don’t update my photos because there’s no technological incentive, and I still have to work everything through Photoshop. More importantly, it’s not a scalable solution both in terms of time and space.

Also, there’s privacy to consider and this is going to be a big deal over the next few years. My brother has always said that he doesn’t want pictures of himself on the web, a little paranoid maybe, but its also his right and I should respect that. My other brother has kids and pictures of them is a whole different ball game. I don’t have the time to develop permissions on my own site so that only family or friends can see them, so why not let flickr do it for me?

I’d always thought of flickr as a site for people who didn’t have their own site, which is of course, ridiculous. For a few quid a month I get to upload an unlimited amount of images at whatever resolution comes off my camera, that’s really good. Not only that, the application interface works better than a desktop operating system, who could have predicted that we would be at this point so soon?

To a certain extent I’m admitting defeat, my photo folder cant possibly keep up with what the people at Yahoo can offer, and to not embrace it would be as pointless as it is unpractical. I know this isn’t in keeping with the pioneering spirit of open source development, but that spirit is based on ideal scenarios of intelligence and time, both of which I don’t have an endless supply of.

So what if the photos aren’t on my site, the web is changing, and that was always going to happen.

There are busy times ahead. The company I work for as a web developer is changing its name, brand and identity. It is, to say the least, a task that involves an incredible amount of commitment and organisation from every aspect of the business.

The initial meetings of a few months ago seemed like a formality, just do this then that then everything else should slot into place, that was the plan anyway. Everything seems so easy when scribbled down in a flow diagram with arrows in yellow highlighter, and I’ve always found that approach to be quite good for holding back from getting stuck in.

There comes a point, as with anything in life, when the talking stops and the physical activity has to begin, which is usually the point where the scale of the undertaking is realised. The web site in question has evolved over a number of years and apart from some basic product titles and codes it is entirely static. It does however employ some fairly cool code that communicates with our CRM and back end on the fly, this is its saving grace.

Photoshop Elements, a fantastic product and a piece of marketing genius. A stripped down version of the fully fledged software install, with all the functionality you’re likely to need unless you work in Hoxton or drink Latte Coffee or wear a Nike Windcheater. Ideal for developers like myself who just need to cut and crop and maybe do bit of contrast correction. It had the Adobe professional interface from Illustrator and Photoshop so if you learnt on one then it’s all easy, same menus, same shortcuts, same everything. All for about £50 – it’s all good, as everyone says now.

So Photoshop Elements, it’s all good. At least it was.

So there I was in one job using my trusty old Elements to great effect, then I got made redundant and moved on to my current position and they used Illustrator for Photo manipulation. Bad as it is impossible. No, “Elements” I said nodding happily, “That’s all I need”.

Elements turns up and it’s version 5 which I start to get exited about. After loading it up however, nothing could have prepared me for the horror that awaited me in my new bling monitor. I actually felt my heart drop with disappointment as I looked at my beloved Elements in utter amazement.

It’s been domesticated. By that I mean it now looks like the kind of thing that you got free with a cheap digital camera in 2003. Gone is the familiar interface, shortcuts and working environment, and in its place are huge buttons and tacky picture album templates. It is, f**king awful. Nothing works now, a prime example is the resize tool that you can no longer constrain with the shift key! The most basic piece of Adobe functionality!

Also, it’s made the Microsoft mistake of trying to be too helpful. It leaves an icon in the tray that leaps into action whenever a new device appears, helpfully looking for photos. “No, stop! Go away, I don’t want you to help me find those pictures tucked away deep in the bottom of my Flash thingy”

So now I’ve got to go back to the IT manager and ask for CS like a greedy student who’s never satisfied. I’ll never use most of the functionality and the company will have to float on the stock market to afford it.

If it’s not broken, please, don’t fix it.