What I build

Web platforms that carry real operations: marketplaces, internal tools, learning systems, customer portals. I own the whole path — requirements, data model, API, interface, deployment — so nothing falls into the gap between "designed" and "running in production".

The experience behind that is not theoretical. BKOTT is a multi-vendor marketplace with catalogue, orders and payments. HDTC is a learning platform with courses, enrolment and assessment. Testat runs live virtual classrooms holding 50+ concurrent users in a single session.

How I work

Discovery first. Before any code we agree on the problem, the users, the data model and what "done" means. That written scope is the thing we measure against later, and it is the reason the budget stays honest.

Then incremental delivery. You get a deployable slice early and a review point every week, not six weeks of silence followed by a demo. Every branch runs through CI and every merge to the main branch is releasable. At RB Agency that rhythm delivered four client platforms in eight months.

What you get

• A production deployment on infrastructure you own: AWS, DigitalOcean, Hetzner or your own Linux servers.
• Source code in your repository from day one, with a readable commit history and no lock-in to me.
• Docker images and a GitHub Actions pipeline, so the next release is a merge rather than an event.
• Written architecture notes: why the schema looks the way it does, which trade-offs were made, what to watch as load grows.
• Arabic and English interfaces where you need them, with RTL treated as a first-class layout instead of a mirrored afterthought.

The stack

Node.js and NestJS, PHP and Laravel, React, Next.js and Angular on TypeScript, with PostgreSQL or MySQL, Redis for caching and queues, and Docker throughout. If your team already has a stack, I work inside it rather than around it.

A good fit if

You have a product to ship and no senior engineer free to own it, or an internal team that needs the architecture and the delivery standard set before the codebase hardens around the wrong decisions.