Taming legacy systems and coding your way out of problems

At the beginning, IT code was king. Every application was carefully hand crafted from scratch by developers who knew the black art of writing code.

As with any industry things have moved on rapidly and now we have an array of application development languages, applications, platforms, tools, cloud services and a whole host of other choices when it comes to delivering software applications to users.

An interesting article spiked my attention the other day that discussed intelligent platforms where business users write their own applications using ‘drag and drop’ controls. It gleefully proclaimed the demise of traditional development approach and presumably the redundancy of leagues of developers.

We all know the march of technology invention is relentless. There may come a day when developing complex applications is as simple as clicking a few buttons. However, I wonder if we will ever eliminate the need for bespoke coding completely?

Sure you can buy an off the shelf apps that delivers most of your requirements but there is always something specific that the application can’t do. These bespoke elements can be straight-forward user interface bells and whistles.

At the other end of the spectrum bespoke code can be used to write entirely new modules or interfaces between systems. You can take data from your internal customer databases and put them into you cloud application. Or write a helpdesk application that allows analysts to update hosted services at the click of a few buttons.

The other main reason for bespoke coding is ownership of the IPR and the application. Developing in the cloud or on application platforms is great until you want to licence and resell your masterpiece. If you don’t own all of the code that runs your application then licensing will be a complicated legal problem. Depending on the other vendors it might be completely impossible or at least result in lengthy negotiations and cost.

One key consideration with writing bespoke applications is to ensure that the development is supported by a robust development process. If it is, then the end result will be a quality application that is tailored to the needs of your users.

SHARETweet about this on TwitterShare on LinkedInShare on FacebookShare on Google+Pin on PinterestDigg thisShare on RedditShare on TumblrShare on StumbleUponEmail this to someone

Thomas Coles co-founded MSM in 1998 and is the largest shareholder with 44.7%. His key achievements so far include growth from 2 to 40 FTE; high levels of customer satisfaction and retention, as well as surviving the sector downturn from 2001-2003 and growing the business in the 2008-2009 recession. Thomas’ business acumen was apparent from a young age. As a child (aged 8) he was already budgeting his pocket money on a spreadsheet. His passion for technology was also evident, as, aged 10 he was writing programmes for his Amstrad. Thomas started the MSM business soon after graduating with his father, who remains a non-executive director today. A strong believer in applying common sense to any situation, Thomas says his objective is to continue to be criticised for being too honest. Away from the office Thomas enjoys family life with his wife and three children and likes to take part in half marathons, going to the gym and watching Formula 1 motor racing. Thomas is also a trustee of a local charity.