Accounting platforms, multi-tenant SaaS, Arabic-first products in production. I start from how the business works — the ledger, the approvals, the edge cases — and design the software around it. Then I teach beginners from that same work.
backend modules in one production accounting platform
members served on a single live deployment
faster core analytics — 1,675ms down to 59ms
documents restored clean in a drilled recovery
Three systems, in production
Business & accounting systems
Double-entry ledgers, AR/AP, inventory, payroll, approval chains. The parts where being wrong costs money.
Multi-tenant SaaS
Tenant isolation, control planes, custom domains, subscription billing — architected before the first customer, not after the tenth.
Arabic-first & RTL products
Arabic as the primary language, not a translation layer bolted on at the end. Layout, data, documents and reports all read right.
Performance & recovery
Slow dashboards, heavy queries, backups nobody has ever tested. Measured before, measured after, restore drilled for real.
Understand
I learn how the business works before writing a line of code.
Model
Data model and architecture first. Most bugs are decisions made here.
Build
Shipped in slices you can use, with tests on the money paths.
Hand over
Documented, backed up, restorable. Your team can run it without me.
- Based in
- Egypt · working across MENA
- Languages
- Arabic · English
- Handle
- @josamcode
- Response
- Within two working days
I build software for clients who need a system, not a website. An accounting platform that a Gulf company closes its books on. A church platform holding 6,400 members' records with backups that have actually been restored. A publishing tool I run my own content through.
The pattern in all of it is the same: understand the business rules properly, model the data carefully, and treat production as something people depend on. Most of what goes wrong in software was decided long before anyone opened an editor.
I teach from that work — in Arabic, for beginners who want to understand how real systems are put together, not how to follow along with a tutorial. Everything I explain is something I have shipped and had to maintain.
Landing-page work, throwaway prototypes, or projects where nobody can answer how the business actually operates. I do my best work where the rules are real and the consequences are too.
A paragraph about the business problem is more useful than a spec. I reply within two working days, and I will tell you plainly if I am not the right person for it.