Reuse - so you don't have to rewite

In 1990s we were using reuse at IBM as a benefit that came with the adoption of engineering C++, then partisipating in IBM Corporate Reuse Council, the Corporate Reuse Environment was built, this also projected reuse-thinking. Barriers to reuse at the time were management or the organization, there was an overhead to it being reusable and to what degree.

In today’s world there are two types of IT system: those that provide you with your core business processes, everybody needs these and requirements are similar – this is the world of the packaged application. Then there is the second category, those that provide the business processes that differentiate you and make you unique. This is the domain of the the bespoke built highly tailored solution. But the boundaries are blurred and if cost permitted, you would prefer to deliver more bespoke solutions. This is where re-use and frameworks are key.

The frameworks that timberzen has developed can cut development time and cost of a bespoke built solutions significantly, in a number of ways:

  • Potted architectures and design patterns can shave weeks or more off the start of a project
  • Re-usable components allow typical generic functions such as workflow to be lifted off the shelf without the need for development
  • Generation frameworks and build environments significantly increase productivity
  • Using previously tried and tested architectures and components reduced testing time and increases reliability
  • Rapid Application Development
    We accept these days using the .NET library gave us a productivity improvement of over 90% of what went before, standing on the shoulders of others we could reduce development time by 60% by using appropriate tooling. The world changed before and after the introduction of Windows Communication Foundation(WCF), then Cloud Services so you don't have to rewrite the plumbing for every project then ending up with a maintenance and version control nightmare. Then we have moved from WCF to ultra lightweight micro-services distributed across the cloud.
    When some Managers don't get is that it takes a few seconds to drop the "asp:Login" login to a page so why does it take so long to so the rest? But the 'rest' is not just wiring up the ASP.NET security framework which is fine for small sites, but when you are looking at large multinational, global sites, then you are worth looking at 'Backend As a Service' provision from the cloud. This is when you can develop Apps in just weeks. Alternativly, there are other development fashion that are not so rapid but have other advantages - which one is right for your project?

The net result being that bespoke solutions can now be delivered in similar time scales and costs as package based offerings, but are tailored to what you are trying to achieve as a business.

Add to this the fact that your solution will be delivered using web based interfaces and built upon open architecture platforms easing integration with package, the total cost of deployment and ownership is significantly reduced.


Learn More