About

I’m Moustafa Abdelsalam, an Oracle APEX and PL/SQL developer in Cairo.

Since 2023 I have been building and maintaining large enterprise APEX applications, laboratory information systems with 100+ pages that hospitals and public-health laboratories use every day, across APEX 20.2, 23.2 and 26.1. The work runs from database design and PL/SQL packages to ORDS REST services, Interactive Grid JavaScript, authorization frameworks, multilingual Arabic/English (RTL) interfaces, and production support on live systems.

Before that I spent seven years in IT infrastructure: Windows Server, networks, backups and user support. That is where I learned to diagnose before I fix. Most posts here start with why is this actually happening?

I’m now learning Python and Node.js by building real tools with them, and the problems I hit there go here too.

Why “Fixed Notes”#

Most of what I know I learned the slow way. A fix looked right, broke something else, and needed a second look. Each post is one of those problems: what happened, why it happened, and the fix that held. I write them down so the next developer spends minutes instead of hours.

How the posts are made#

• Every post starts from a real problem, rewritten as a small, neutral example. No client code, schema or data is ever published here.
• Every fix was verified on a real version, and the post names it: the APEX release where I hit the problem and fixed it (20.2, 23.2 or 26.1), or for example “Python 3.12”. When I can also check it on another release (I keep a local APEX 26.1 sandbox), the post says what changed. When I could not, it says so instead of guessing.
• Corrections are welcome. If a post is wrong for your version, tell me. I’ll test it and update the post, with the date of the change.

I use AI tools to help with editing and formatting. The problems, the tests and the conclusions are mine.

This site is independent and is not affiliated with Oracle or any other vendor mentioned in it.