Backend systems that keep an honest record of what happened.
I design and build backend systems and desktop applications — from point-of-sale software with tamper-proof financial records to web platforms — with a security engineer's instinct for what can go wrong.
01 / ABOUT
A backend developer who treats data like evidence.
I'm a computer science graduate from Libya working across PHP/Laravel, .NET, and MySQL, with a habit of designing systems around one question: if this record is ever disputed, can the data prove what really happened?
That question shaped my graduation project — a migrant worker registration system built for Zliten Municipality — and it now drives the point-of-sale platform I'm building, where every invoice is immutable by design: corrections happen through linked return records, never edits.
In parallel, I'm working toward SOC Level 3 in cybersecurity, starting from the internals of how systems fail — hash collisions, password storage, log analysis — because software that handles money and identity has to be built by someone who thinks about how it breaks.
- BASE
- Tripoli, Libya
- ROOTS
- Zliten, Libya
- FOCUS
- Backend · Desktop · Security
- BUILDING
- A software company — POS, web, mobile
- STUDYING
- TryHackMe SOC L1 → L3
02 / STACK
The stack, layered like the systems I build.
Top to bottom, the same order I reason about a request: what the user touches, what processes it, what stores it, and what protects it.
Interfaces
Backend & APIs
Data
Security
03 / LOG
Project history.
The work that shaped how I build — kept in the order it happened.
POS System — Desktop
A point-of-sale desktop application built around one non-negotiable rule: financial records don't get edited, they get corrected. Invoices, prices, and tax are snapshotted at the moment of sale; returns and voids are separate linked records, so the history stays provable. Layered as Presentation / Business Logic / Data Access, with domain models for products, invoices, payments, and stock movements.
Migrant Worker Registration System
A registration and management platform built for Zliten Municipality to track migrant worker records. Developed with an Agile/Scrum process, backed by full system analysis and design — class diagrams, ERDs, and a normalized database — and grounded throughout in peer-reviewed research rather than informal sources.
.NET Backend Roadmap
An interactive roadmap built to plan my own path to senior backend engineering — 75+ concepts organized across 7 layers, from language fundamentals through architecture and deployment, with progress tracking so the plan stays honest about what's actually done.
04 / PATH
Route to SOC Level 3.
Running in parallel with the backend work, plus AZ-204 as the cloud track for where the company is headed next.
Building something that needs a backend?
Open to backend and desktop app work, POS/systems projects, and conversations about security-minded software.