• How incredibly fast you can build a working prototype

• How to use GitHub Actions effectively

• How to test a Node.js application locally

• How to use PM2 and Nginx for these kinds of setups

• That the system can often fix itself in a loop

I also learned that for every project, I want to include some kind of admin panel — a place where I can configure endpoints, passwords, URLs, settings, SMTP, etc. This avoids scattering things across hidden credential stores or framework configs.

And how surprisingly easy it is to generate a PDF from an invoice without overthinking templates
(no Word templates, no AOP, no PL/SQL-to-PDF).

At the same time, I realized how little I sometimes needed to know about the actual code, because my experience told me where the open issues would be — like responsive/mobile design. And even those were solved with a few additional coworking sessions.

Now you could ask: how much did I really know about Oracle APEX code?
Fair point — in many ways, I was mostly configuring there as well. But I do understand what’s happening inside an Oracle database: PL/SQL, tables, SQL, plus some JS libraries integrated by APEX. That comes from years of using it and getting fast results.

Over time in APEX, we learned to work around its limitations — especially in usability (e.g. Interactive Grid) and design. We built our own plugins, template components, and JS libraries. Looking back, I underestimated how much time and energy that actually cost.

But AI doesn’t just help with those areas — it also builds a fitting ER model in the background, configures APIs for integrations with other services like Stripe, and handles a lot of the plumbing automatically.
In Oracle, we used to set up PL/SQL or APEX_WEB_SERVICE API routes ourselves, extend the data model manually, regenerate APIs, and so on. Now, AI coding tools take over much of that work.

I’m excited to see APEX evolve further and to use AI tools to tackle these APEX-specific challenges faster, more easily, and more sustainably.

For my private projects, however, I no longer use APEX — they’re simply too small, and the Oracle stack feels too heavy for that use case.

But maybe… just maybe… that will change again someday. If it does, you’ll see it on my APEX blog.

my APEX Blog

My Tipp 1 => check Your Claude Code with Codex or vice-versa - for GDPR, Security issues etc.
My Tipp 2 => Ask before starting coding => is sveltje kit for this project a benefit or another framework to get out less codes in repo and safe some tokens.

👉 Yaitcon.hasnode.dev – my APEX blog