Blog: Rick Barton Subscribe to this blog's RSS feed!

Rick Barton

Hello and welcome to my blog. I am delighted to blog for the BeyeNETWORK, and I'm really looking forward to sharing some of my thoughts with you. My main focus will be data integration, although I don't plan to restrict myself just to this topic. Data integration is a very exciting space at the moment, and there is a lot to blog about. But there is also a big, wide IT and business world out there that I'd like to delve into when it seems relevant. I hope this blog will stimulate, occasionally educate and, who knows, possibly even entertain. In turn, I wish to expand my own knowledge and hope to achieve this through feedback from you, the community, so if you can spare the time please do get involved. Rick

About the author >

Rick is the director (and founder) at edexe. He has more than 20 years of IT delivery experience, ranging from complex technical development through to strategic DI consultancy for FTSE 100 companies. With more than 10 years of DI experience from hands-on development to architecture and consulting and everything in between, Rick’s particular passion is how to successfully adopt and leverage DI tools within an enterprise setting. Rick can be contacted directly at rick.barton@edexe.com.

June 2009 Archives

I was driving home last week listening to the radio, when an article came on discussing alternative energy sources.  A stray right brain neuron must have fired and I began wondering how what we do in DI impacts on the environment.  After all almost every other technology has some kind of environmental grading.  Certainly my fridge and my car do, and every company is aware of the impact of their hardware consumption, but there seems to be little consideration as to whether software can have an impact on carbon footprint.

It is generally recognised that code (correctly) created using DI tools is more performant than hand cranked code.  This means that less hardware is used to perform the same actions.  Less hardware means lower carbon footprint, means more environmentally friendly.

This is even more profound when one considers the MPP technologies that can dramatically increase performance and scalability.  If one can negate the need for new hardware or even remove existing infrastructure then the impact is not only positive from an environmental perspective, but also from a cost perspective.

And so I have arrived at the conclusion that DI tools are at the positive end of the green scale and perhaps performance should be given a higher priority when evaluating software.

Extending this argument slightly, should software vendors be touting their green credentials?  Should there perhaps be benchmarks that could provide an "energy rating" for software?

If  this did happen then one would hope we would see a return to leaner code and more efficient programming practices, meaning that we are all less likely to hear the words "just throw some more tin at it"


Posted June 30, 2009 12:10 PM
Permalink | No Comments |