Feb 01, 2017 Blog, Oracle 0 comment

Oracle Apex Manages Your Technical Debt

Technical debt refers to the cost of cutting corners when developing software – and we all know that corners are cut so that the software can be ready on time and on budget.  But what seems like the right thing to do at the time can become very expensive.  Speeding development has its price – the danger comes in when the debt isn’t paid:  software rewrites and upgrades must be made promptly because a higher price will have to be paid for every day spent working with code that is not quite right. Companies who understand that technical debt will only increase over time will focus on refactoring their code.  The trick is to minimise the initial technical debt. Oracle APEX offers a cost effective way to do this.

How is your company incurring technical debt?

In the hurry to get software developed means that technical debt is commonly caused by 3 factors:

  1. Bad Architectural Design – this includes functions that are not modular resulting in the software that is not flexible enough to adapt to changes in business needs.
  2. Inconsistent or Poor Code Quality – this includes lack of alignment to industry standards, best practice, features and frameworks.
  3. Lack of Test Coverage – resulting in quick-fixes and patches.

Reduce debt with Oracle APEX

Companies would be wise to limit their initial technical debt, and this means finding a way to avoid or mitigate these common causes. Bad architectural design and poor code quality is easily addressed with Oracle APEX in the following ways:

  • APEX Advisor: Testing is vital, and the APEX Advisor enables you to check the integrity and quality of your application with compilers that flag errors or suspicious behaviour. When running Advisor, invalid developer code that was previously ignored may now produce an error because of tightened rules.
  • PL/SQL Packages: APEX specifically targets inconsistent or poor code quality by minimising code duplication. Business logic is easily reused by moving PL/SQL code to packages in the database from your APEX application.
  • User Interface (UI) Defaults: Maintaining consistency across multiple pages in an application is made possible with Oracle APEX. UI defaults allow you to assign properties or create a specified schema for tables and views. This information will be used by a wizard to create default values for region and item properties.
  • Subscriptions: In this day and age, when corporate identities and branding serve to draw and retain customer trust, it is vital that your look and feel is carried throughout. Subscriptions facilitate the easy maintenance of a consistent corporate look by allowing for sharing of templates across multiple applications.
  • Shared Components: Apex boasts a range of components from code snippets to processes that allow re-usability across applications lowering maintenance overhead for future iterations.

To find out how Oracle APEX can minimise your initial technical debt, contact the experts at HeadByte.