For many years, businesses have had someone in a department who was particularly good with Excel or Microsoft Access. They weren’t an IT professional, but they understood the work and knew enough to build something useful.
What started as a spreadsheet to save a few hours gradually became the system everyone relied on. More data, more formulas, a few macros, perhaps a link to another file on a shared drive. Then the person who built it left.
Suddenly, nobody quite understood how it worked. Documentation was sparse, several versions were in circulation, and nobody was certain which one was being backed up. Meanwhile, the business had outgrown it.
The original idea was often a good one. Someone had spotted a problem and done something useful about it. The difficulty came when a departmental tool became an essential business system without the support it now needed.
Vibe coding, using conversational prompts to get AI to generate and change software, often without closely examining the underlying code, brings that familiar challenge back, only faster.
It gives people who understand their business processes another way to improve them. An idea can become a working application remarkably quickly. That creates real opportunities to experiment, reduce repetitive work and solve problems that might otherwise remain on a development backlog. But a successful demonstration is only the beginning.
The demonstration may show what happens when the data is correct, users follow the expected steps, and every connection works (the 'happy path'). Everyday business use introduces more variation.
An integration fails. Someone enters something unexpected. An update breaks a report just before month-end. The person who created the application is on holiday, and the business needs it fixed that morning.
At that point, ownership and maintenance become a very practical concern. Who supports the application? Where does it run? What changed? How can service be restored safely?
There is also the platform itself to consider. What happens if the subscription becomes too expensive, or the organisation decides to stop using it? Exporting the code and data may help, but someone still needs the skills and infrastructure to run, maintain or replace the system.
For organisations using or considering Oracle APEX, APEXlang offers a way to bring more structure to AI-assisted development.
APEXlang is Oracle’s human-readable format for defining APEX applications. It represents application definitions as structured text files that developers and AI coding assistants can generate and edit, and that teams can validate, review and track in version control.
The practical benefit is a clearer record for the people maintaining the application. They can inspect its definition, compare changes and continue development without relying on the original creator’s conversation with an AI assistant.
That supports maintenance within APEX. Moving to another platform still requires a separate assessment of the application, its data and its dependencies.
Oracle APEX also provides built-in security capabilities, including controls for authentication, access permissions, session management and protection against URL tampering. Escaping mechanisms help protect against cross-site scripting.
These capabilities can reduce the amount of security functionality a team needs to assemble itself. They still need to be configured and used correctly, with careful review of permissions, sensitive-data access and custom code.
Tools and platform capabilities need a process around them.
As an application becomes important to the business, there should be clear answers to a few questions:
Who owns it, and who can support it when the creator is unavailable?
How are changes reviewed, tested and released?
How will someone know when it fails?
Can its data and service be recovered?
What would it take to move or replace it?
The level of formality should match the importance of the system. A small experiment does not need the same oversight as an application used to process orders or manage customer information. As the business becomes more dependent on it, the way it is managed must reflect that.
We have learnt this lesson with spreadsheets and Access databases. With AI, we have an opportunity to apply it earlier and give useful ideas the support they need to become dependable business applications.
If you’re exploring AI-assisted development, get in touch to discuss how Oracle APEX could help you improve productivity and build applications your team can maintain.