Ahmed Al-HawajriLaravel & PHP Developer

Available for remote workGaza, Palestine

Laravel · PHP · MySQL · Vue 3

I build the whole system,and test it before you see it.

I build booking systems, online stores and admin dashboards in Arabic and English, with Laravel and MySQL on the back end and Vue 3 on the front.

  • Database
  • Server & API
  • Interface
  • Tests
  • Security

Why me

Most problems on a website never show on the screen. They show when two people buy the last piece in the same second, or when a visitor in another country books at the wrong hour. That is where I start: I write the rule first, then the test that proves it, then the screen that carries it.

The work

Five projects, five real problems

Each one started with a plain question from the people it was for. Here are the questions, and how I answered them.

  1. Diwan2026

    Arabic-first furniture store for the Saudi marketIndependent project · open source

    Every piece tells the buyer, before they pay, if it fits the room and gets through the door.

    The problemFurniture is where buying online fails most: a centimetre figure means nothing for the buyer’s room, so the piece arrives and does not clear the door.

    • Laravel 12
    • PHP 8.2
    • MySQL
    • Blade
  2. Waeda2026

    Appointment booking for service businessesIndependent project · open source

    Customers book from their phone with no account, and an appointment guard keeps booked times from going empty.

    The problemThe real loss for a business is not too few bookings but no-shows: a booked time left empty because the customer did not come.

    • Laravel 12
    • MySQL
    • Vue 3.5
    • Vite 6
  3. Opsight2026

    Operations and business intelligence for Gulf businessesIndependent project · public repository

    Your orders, stock and expenses in one place, and their figures against the period before.

    The problemOrders in one place, stock in another, expenses in a spreadsheet, so nobody knows what last month’s profit was or why it moved.

    • Next.js 16
    • React 19
    • Tailwind 4
    • TanStack Query
  4. Takharruj2026

    Graduation project management platformIndependent project · open source

    A graduation project from first idea to final grade, in one place for the student, the supervisor and the department.

    The problemThe information lives in spreadsheets, WhatsApp and email, so nobody can quickly say which groups have no supervisor, which milestones are late, or who changed a grade.

    • Laravel 12
    • PHP 8.2
    • MySQL
    • Blade
  5. Lamma2026

    Orphan sponsorship platformIndependent project · open source

    Sponsor a named child within their own family, and see where your money went.

    The problemMost donation sites ask you to trust them: you give to an anonymous cause and never see what arrived and what was spent.

    • Laravel 12
    • PHP 8.2
    • MySQL
    • Blade

Services

What I can build for you

Pick the one that sounds like your project. Next to each is a real project where I’ve done exactly that, so you don’t have to take my word for it.

Also

I also take on , , and .

A schema that stops the mistake before it happens, and a documented API held up by tests.

Built in Lamma

Problems and solutions

Problems I ran into, and how I solved them

The hardest part of any project never shows on the screen. These are real situations from my projects: the problem, the decision I made, and the test that keeps it from coming back.

  1. Waeda

    Two customers ask for the same slot at the same moment.

    How I solved it

    The API locks the resource row before testing for an overlap, inside the transaction that writes the booking.

    passedConcurrentBookingTestView the code on GitHub

  2. Diwan

    Two customers buy the last piece in stock at once.

    How I solved it

    Checkout locks the product row with lockForUpdate inside the transaction that writes the order.

    passedStockTestView the code on GitHub

  3. Diwan

    Retiring a piece used to erase it from every past order.

    How I solved it

    The columns release instead of cascading, and a name and image snapshot travel with the line.

    passedOrderHistoryTestView the code on GitHub

  4. Lamma

    One person records a disbursement and signs it off themselves.

    How I solved it

    The policy checks that in code rather than in the interface, and an approved record is reversed with a counter-entry rather than edited.

    passedDisbursementRecordTestView the code on GitHub

  5. Opsight

    A cost hidden on screen is still there for anyone who opens the browser’s tools.

    How I solved it

    A field a role may not see is left out of the API response itself, not hidden in the interface.

    passedFieldRedactionTestView the code on GitHub

  6. Diwan

    A sofa that fits the room sticks in the lift or at the turn of the stairs.

    How I solved it

    The way in is walked step by step with a 2 cm margin a side; the worst step decides, and an unmeasured one stays unchecked.

    passedPassageTestView the code on GitHub

  7. Lamma

    The page that finds the least-funded children slowed down as more were added.

    How I solved it

    Both sort directions were made the same so the engine reads the index backwards, served by an index on (status, funded_percent, id).

    passedOrphanGridSortTestView the code on GitHub

Behind the screen

What you don’t see on the screen is what protects it.

Scroll to see what happens behind a single button: a request through the server and the database, the tests that guard it, and a layer that turns away anyone who has no business being there.

  1. Interface

    Arabic and right to left from the first line, telling people in their own language what is happening and what to do next.

  2. Server & API

    Prices, stock and permissions are settled on the server, inside one transaction. Nothing that matters is left to what the browser sends.

  3. Database

    I design the tables so the schema itself stops the mistake before it happens, instead of us finding it after it has cost you.

  4. Tests

    Every rule your business depends on is guarded by a test that runs on every change, so a bug we fixed never quietly comes back.

  5. Security

    A request with no right to be there is turned away at the server’s door, not by hiding a button. Your customers’ data stays theirs.

Engineering rules

Six rules I don’t bend

Each one came from a real problem in an earlier project, which is why I don’t leave them to chance in yours.

Arabic from the first line

Direction is built into the layout, not mirrored at the end. Numbers, icons and filters stay where they belong.

Came fromDiwanWaedaTakharrujLammaOpsight

Rules live in the data layer

Permissions, stock and concurrency are settled in the database inside the same transaction, not by hiding a button in the interface.

Came fromDiwanWaeda

A test for every rule that matters

Anything no test checks will break after the first edit somebody writes after me. Even the design-system rules are written as tests.

Came fromDiwanWaedaTakharruj

Store the fact, derive the rest

A date of birth rather than an age; free slots generated from rules rather than written into a table. A number saved twice will disagree one day.

Came fromLammaWaeda

History is never deleted

An order line outlives the product; an approved entry is reversed with a counter-entry, never edited. What actually happened must stay readable.

Came fromDiwanLamma

Works at 500 rows like at 5,000

Pagination, sorting and search happen in the database, not the browser, and a duplicate request is rejected by the engine, not by code discipline.

Came fromTakharrujLamma

The tools

What I work with, and where

No stars, no percentages. Each coloured dot means the tool is actually used in that project, and you can open it and see.

What I work with, and where
DiwanWaedaOpsightTakharrujLamma
Backend & databaseBusiness logic, permissions and transactions on the server, on MySQL schemas designed from scratch.
LaravelDiwanWaedaOpsightTakharrujLamma
PHPDiwanWaedaOpsightTakharrujLamma
MySQLDiwanWaedaOpsightTakharrujLamma
REST APInot usedWaedaOpsightnot usedLamma
Frontend developmentVue or React, chosen per project: a Vue console, a Next.js app.
Vue 3not usedWaedanot usednot usedLamma
Reactnot usednot usedOpsightTakharrujnot used
Next.jsnot usednot usedOpsightTakharrujnot used
UI developmentResponsive interfaces in Arabic and English, right to left and left to right.
Tailwind CSSDiwanWaedaOpsightTakharrujLamma
Engineering & testingPHP tests for the rules, Vitest for the interface logic, Playwright in the browser.
PestDiwannot usedOpsightnot usedLamma
PHPUnitnot usedWaedanot usedTakharrujnot used
Vitestnot usedWaedaOpsightnot usedLamma
Playwrightnot usedWaedaOpsightnot usedLamma
AI integrationModels like Claude wired to the app’s own data and rules, with answers held to a fixed shape and read-only tools.
Claude APIDiwannot usednot usednot usednot used

How I work

From your first message to handover

Five stages, so you know what happens after you write to me and what you receive at each one.

Start a project
  1. Understand what you need

    You describe the project in your own words; no technical spec needed. I reply within a working day with the questions that pin down the scope and its hardest part.

  2. Agree the scope and the plan

    A written scope: the screens, the roles, the data and the rules. The price is fixed once the scope is agreed.

  3. Build it in stages

    The work is split into milestones, and payment follows them: a part at the start, then a part as each stage is delivered.

  4. Test the rules that matter

    Prices, stock, permissions and bookings are guarded by automated tests that run on every change, so a bug we fixed stays fixed.

  5. Review, then hand over

    You try the working application before handover. Support after delivery is agreed in the proposal.

Behind the camera

Ahmed Al-Hawajri

Ahmed Al-Hawajri

Laravel & PHP Developer · Gaza, Palestine

I don’t start from the screens. I start from the rules.

I’m Ahmed, a developer from Gaza. I build complete web applications on my own, and what I care about most isn’t how a screen looks but what happens when people actually use it.

The rules I work by weren’t decided in advance; each one came from a mistake. In Diwan, removing a product from the catalogue used to erase it from every past order, until I understood that a record of what happened doesn’t follow what’s on sale today. Since then it’s a written rule, with a test beside it.

All the code on GitHub

The next project starts with a question from you. Tell me what’s getting in your way at work today, and we’ll work out how to fix it together.

Let’s start your project

Write in your own words; you don’t need a technical spec. I’ll reply within a working day with questions that pin down what we’re building and its hardest part.

What happens next

  1. You describe the projectA blank page or an existing codebase, however rough the idea is.
  2. I reply within a working dayWith the questions that pin down the scope and the hardest part.
  3. We agree, then startA clear scope and steps before the first line of code.

Or directly

ahmedalhawajri89@gmail.comWhatsApp

All fields are required

What is it about?

At least 20 characters

Goes straight to my inbox.

  • No commitment
  • Arabic or English