Full-Stack Web DeveloperIslamabad, Pakistan
I'm a full-stack developer in Islamabad. Most of what I build is operational software — the systems a business opens every morning: payroll, attendance, admissions, orders. The kind of software where being wrong has a cost that shows up in someone's salary.
I also build the sites that sit in front of those businesses, because a company is usually judged on the marketing site long before anyone sees the system behind it.
01
A system that arrives full of fabricated staff and invented numbers teaches the client to distrust every figure in it. Mine ship empty: the seed creates one account and the settings, and the first data you see is your own.
Al-Aziz Workforce OS — the demo dataset is gated behind a flag and off by default
02
Security that depends on remembering to add a guard will eventually be forgotten. So the default is denial: everything is protected unless a handler explicitly opts out, which turns a forgotten guard into a locked door rather than an open one.
Air Foundation — a global guard protects every route; a permission absent from the catalogue can never pass
03
The expensive rewrites I have seen all start the same way: the interface knows too much about where its data comes from. A service layer with two implementations costs a day early and saves a month later.
Al-Aziz — one environment variable swaps the whole UI between fixtures and the live API, without touching a component
04
The handover is part of the build, not an afterthought once the invoice clears. If you cannot run the project from its README on a clean machine, it is not finished — and you should not be dependent on me to keep it alive.
Every repository ships setup, architecture and deployment documentation
05
Design decisions should be defensible with a number. Where something can be measured — a contrast ratio, a load time, the exact position of a horizon in a photograph — it gets measured rather than eyeballed.
This site's headline geometry is computed from a script, not tuned by hand
I studied Computer Science at Bahria University in Islamabad. I joined GSM Player as an intern and stayed on as a developer, which is where I learned the difference between code that works and code that keeps working — a distinction coursework never quite reaches.
Most of the last two years has gone into Dervi, an app I have been building that whole time and by some distance the longest I have worked on one thing. The rest is what is on this site: a restaurant's payroll and attendance system, a multi-tenant school platform, and a content platform built before its catalogue.
