For this series, I want to explore AI beyond writing code: using those same tools to understand what happened when an application does not behave as expected. The work between a screenshot and a diagnosis involves finding the execution, connecting its records, and deciding where to inspect the code. An early assumption can send that…
I have spent enough time reviewing enterprise applications to know that the first successful run is rarely the difficult part. The difficult part begins later, when someone has to explain why a user can see a page, where a secret is stored, which code changes data, how a session value arrived there, and what must…
There was a point when one of my report queries stopped returning only business data. It also decided which CSS class represented an error, assembled pieces of HTML, omitted empty messages, and formatted small lists of labels. The report still worked, but the SQL had quietly become part query and part user interface. I love…
An Oracle APEX service-candidate search that keeps the 384-number embedding behind the application boundary.
I had been waiting for my Oracle APEX environment on OCI to be updated to version 26. This week it finally happened. So, to celebrate properly, I decided to build a small field-style demo around one of the features that immediately caught my attention in this release: native AI Agents in Oracle APEX. The interesting…
Most of the time, when I build an APEX page, I try to stay inside the declarative model for as long as the page still feels honest. Native regions, template components, lists, cards, reports, buttons, dynamic actions, and Universal Theme options are usually easier to maintain because they remain visible in the Builder and other…
User feedback has a bad reputation among developers. It arrives without reproduction steps. It calls an unclear label a bug and a business-rule disagreement a system failure. Sometimes it appears in a meeting three weeks after the user quietly found another way to finish the work. It is tempting to treat feedback as a necessary…
A deep dive into Oracle APEX URLs: request, clear cache, debug, Interactive Reports, authentication switching, session state, and secure URL generation. Understanding URL parameters changes how you design APEX applications.
In the first version of this case, I deliberately kept things focused. The goal was to prove that a user could come in through Google, complete a minimal onboarding flow, receive ORDS client credentials, and actually use those credentials against a protected endpoint. That loop, once it closes, already carries a lot of value, and…
In APEX, the usual paths are familiar: workspace users, database accounts, or some internal authentication model we control ourselves. But APEX also gives us Social Sign-In, and that changes the tone of the application completely. There are several ways to do that depending on the provider, but in this case I am using Google because…