About
Systems that generate systems.
An architect-minded engineer who builds systems that generate systems — and the studio and lab that produce them.
I build systems that generate systems. A single source of truth becomes a website, a résumé, PDFs, an AI context, a search index — generated, never hand-maintained. A recurring problem becomes a library other systems install; a slow workflow becomes a tool, and increasingly an agent, that does the work. I optimize for leverage : the artifact that produces other artifacts, on a foundation of type safety and long-term maintainability.
I run two engines at once, and they feed each other. The studio is delivery — I architect and ship production systems across Laravel, TypeScript, and .NET: governance platforms, SaaS, CRMs, logistics, clinics, mobile apps — owned end-to-end, from backend to deploy. The lab is infrastructure — I turn the recurring problems from delivery into reusable packages, agent tooling, and developer-experience automation. The lab sharpens the studio; the studio funds and grounds the lab.
The arc runs through three ecosystems. I originated in PHP/Laravel and built deep product fluency there — still the spine of the studio. From that foundation I expanded into TypeScript, React and Next across web and React Native mobile, then into .NET and C# for governance and licensing systems, deliberately carrying library-design taste between languages. Most recently, AI and agentic engineering moved from interest to practice: shipped agent tooling, personalized-learning systems, and AI woven into delivery.
I'm Sudanese, based in Saudi Arabia, with a recurring thread of culturally-grounded products for MENA and Sudan — alongside open source. The throughline of everything: don't solve the same problem twice. Extract it, make it composable, make it generate.
What I value
- Technical lead of a software studio — the delivery, and the tooling beneath it.
- Carry library-design taste across three ecosystems; earn abstractions from real, repeated delivery.
- Build culturally-grounded products for MENA and Sudan, alongside open source.
How I decide
Reach for leverage first
Before building the thing, ask whether I should build the thing that builds the thing. The artifact that produces other artifacts wins.
Make the source of truth singular
Generate presentation from content; never let derived artifacts drift. One edit should propagate everywhere.
Design the interface before the implementation
A clean drop-in API that adds capability without owning your app's architecture — additive, not invasive — is the goal.
Carry taste across ecosystems
Port proven patterns deliberately — bring Laravel-ecosystem ergonomics into .NET — rather than reinventing per language.
Forward-only and reproducible
Schema changes, environments, and setups are scripted and replayable, not hand-tweaked. Reproduce the path, don't patch the state.
Earn the abstraction
Extract a library only once the pattern has recurred and proven its shape in real delivery — never speculate it.
Selected achievements
Architected a technology-governance platform aligning IT operations to COBIT 2019, ISO 9001/27001 and ITIL 4 — controls, audits, risk and compliance workflows in one system. · Architect & lead engineer
Shipped a composable .NET library ecosystem — a cohesive family of drop-in packages plus a generator that scaffolds production-ready projects. · Open source
Built distributed-systems packages for Laravel: peer-to-peer cross-instance sync (outbox/inbox, signed-webhook transport, conflict resolution) and a replicated filesystem driver with reconciliation.
Designed two-sided software-licensing infrastructure for self-hosted Docker products — a vendor authority issuing activations and a brand-agnostic field control panel, with hardware-fingerprint drift tracking.
Shipped AI agent orchestration tooling — parallel multi-agent fan-out with dependency-graph scheduling and merge gating, plus a full-stack browser-QA agent that verifies persisted state. · Open source
Built a declarative engine that manufactures a fully-configured developer workstation, unattended, in minutes — idempotent verify-guarded installs, ~887 tests, governed by a written constitution. · Open source
Delivered production systems across many domains in parallel — governance, software licensing, logistics with government integration, healthcare, CRM, HR, and real-time AI — not one product in one vertical. · Studio portfolio
Questions people ask
What do you actually do?
I'm a software architect and technical lead. I own systems end-to-end — backend, frontend, mobile, infrastructure, the deploy — and I design libraries, not just applications, in two ecosystems. Day to day that's studio delivery plus the reusable infrastructure underneath it.
Which stack are you strongest in?
Laravel/PHP is the production spine — expert level. TypeScript (React, Next, Astro) and .NET/C# are where the library and AI work concentrate. I carry the same design taste across all three rather than living in one.
Are you open to roles, contracts, or advisory?
Yes — architecture, lead engineering, and library/platform work are the best fit. The fastest way to reach me is email; the résumé and selected work cover the specifics.
Why is so much of your work anonymized?
Most studio delivery is client work under NDA. I publish the capability and the technical substance — the brand is withheld and named on request. Open-source projects carry their real names and links.
How do you work with AI?
Woven through, not bolted on. I ship agent tooling and AI features in real products, and I use agents to build — parallel fan-out and automated QA that verifies persisted state — as delivery leverage, not a demo.
Where are you based, and does timezone matter?
Sudanese by nationality, based in Saudi Arabia. I work async-first and have delivered across distributed teams and timezones — a few hours of overlap is plenty.