From Electrical Engineering to Software Architecture
My first line of code was PHP, back in 2006. Building forum templates as a hobby. I was 14.
From there it was C, C++, WordPress, and years of tinkering before I ever considered software as a career. I studied Electrical Engineering in university. Not computer science. That's where I learned to think about systems in terms of data flow, constraints, and failure points. I still design backends the same way. What happens when traffic spikes. What breaks when a payment webhook fires twice. Where the data bottleneck actually is.
I went professional in 2016, starting with Java, Flutter, and raw PHP before landing on Laravel in 2019. Since then, it's been Laravel for everything: SaaS platforms, e-commerce systems, payment integrations, API architectures. It's where I do my best work.
I work from the UAE, remotely, for clients worldwide. Full-time freelancer. This is my career, not a side project.
"I still design backends the way I learned to think about circuits. What breaks. Where the bottleneck is. What happens under load."
Years Professional
Laravel Since
Production Systems Shipped
Based, Remote Worldwide
Philosophy
How I Think About Code
I don't start with code. I start with the business problem. What's the revenue model. How users move through the system. Where this thing needs to scale in six months. Those questions decide the architecture before I open an editor.
Clarity
I write code that other developers can pick up without a walkthrough. Service layers, consistent naming, tested logic. If I get hit by a bus, your project doesn't die with me.
Scalability
Architecture decisions on day one determine whether the system survives year two. I design for where the project is going, not just where it is now.
Performance
Caching, queue workers, optimized queries. I don't wait for something to be slow and then fix it. The infrastructure is there from the start.
What I build
Services
SaaS Platforms
Multi-tenant architecture with isolated data per tenant, subscription billing, role-based access, and infrastructure that handles hundreds of tenants without slowing down.
E-Commerce Systems
Custom-built storefronts with real checkout flows, payment gateway integration, shipping APIs, and server-side analytics tracking that captures what browser pixels miss.
Websites & Web Applications
Company websites, portfolio sites, landing pages, content platforms, ERPs. Not every project is a SaaS or an e-commerce store. Whatever the type, it gets the same architecture, the same testing, and the same attention to performance.
Admin Panels & Dashboards
Internal tools for your team. Order management, commission tracking, user administration, reporting. Designed around how your business actually operates, not a generic template.
API Development
RESTful APIs with proper authentication, rate limiting, and documentation. Built for mobile apps, third-party integrations, or connecting your system to external services like WhatsApp, shipping providers, or payment processors.
Performance Optimization
Slow queries, missing indexes, no caching, overloaded servers. I find what's actually bottlenecking your system. Database tuning, caching layers, queue workers for background jobs.
Process
How I Work
I start with business logic, not code. Revenue model, user roles, scaling expectations, operational bottlenecks. That's what shapes the architecture. I work independently, but bring in trusted designers and developers when a project needs it.
Discovery & Architecture
Before I write anything, I need to understand how your business works. Who uses the system, how money flows through it, what's expected in six months versus day one. The architecture comes from those answers.
Build & Test in Parallel
I write tests alongside the code, not after. Every feature gets built with service layers, proper structure, and test coverage from the first commit. Nothing ships without passing the suite.
Review & Iterate
You see working builds throughout the process, not just at the end. Feedback loops are short. If something needs to change, it changes before the codebase gets too deep.
Deploy & Hand Off
Production deployment with proper infrastructure, monitoring, and documentation. When I hand off a project, the next developer — or you — can understand what's there and why.
Why me
What You Get
An engineer, not just a developer.
I studied Electrical Engineering. I think in systems, constraints, and failure modes. That's not a metaphor — it's how I was trained.
Someone who's built this before.
Multi-tenant SaaS, custom e-commerce, server-side analytics, bilingual systems, portfolio sites, landing pages, ERPs, content platforms. Different projects, same approach — clean architecture, tested code, built to hold up.
Code your next developer can read.
I won't be on your project forever. Everything I build is documented, tested, and structured so the next person doesn't need me to explain it.
One person, full ownership.
I'm a full-time freelancer. No agency overhead, no handoffs between departments, no "let me check with my team." You talk to the person writing the code.
Arabic and English, natively.
Not just translation — I build systems that work properly in both directions. RTL layouts, Arabic typography, bilingual content management. I speak both languages and I build for both.
Business logic first, code second
I don't open an editor until I understand how your business makes money, who your users are, and where the system needs to be in six months. The architecture comes from those answers, not from a template.