Founder & CTO of Tritech Solutions. Six years of shipped products.
Based in Pakistan. Tritech is a software consultancy I founded in 2019 — it serves international clients across healthcare, fintech, e-commerce, and AI. I own the architecture, hands-on development, and cloud infrastructure. When a project needs a team, I hire and lead it.
I started Tritech as a freelancer in 2019 and grew it into a consultancy leading multi-engineer engagements for clients in the US, Germany, UAE, and South Korea. I've shipped 20+ products end-to-end: EHR platforms handling 2M+ records, Web3 SDKs on Solana, AWS infrastructure built from scratch, multi-region e-commerce, and AI-powered messaging systems.
Formally trained at UET Peshawar (B.Sc. Computer Systems Engineering, 2021), but the job itself I learned by shipping. That shapes how I work: I care about the parts of the stack that are expensive to get wrong — infrastructure cost, data model, failure modes, the boundary between what a system does and what it merely claims to do.
I'd rather read a provider's docs and a flame graph than a conference talk. I'd rather fix a production bug at 2 a.m. than ship something I wouldn't run myself.
What I'm drawn to: cost-efficient infrastructure, owning the whole stack, and systems that actually run in production. Healthcare records under HIPAA. Web3 checkout that survives provider outages. AI-office tooling grounded in real corpora. E-commerce on AWS built the way it should have been from day one. If the interesting part of the problem is the real-world operating conditions, I'm probably interested.
Outside client work, I've trained 1,800+ students from underserved communities in Flutter through the Youth Education Festival — many of whom now earn freelance income of their own. The shape of the company matches the shape of the promise.
Rules I apply by default.
Not laws. Defaults exist so you notice when you're departing from one. Each of these is a mistake I've made at least once.
Boring is a feature.
Postgres, not a distributed K/V. Systemd, not a custom supervisor. The threshold to adopt something exotic is high — "it's interesting" doesn't clear it.
The interesting code is the code that decides when not to trust itself.
Happy paths are tutorial pages. Staleness, failover, idempotency, confidence floors — that's where the engineering is.
Write decisions down.
The future version of me, six months from now, will not remember why. One file per decision, five minutes to write, saves hours later.
Two of everything that matters.
Two RPC providers. Two DNS. Two backup destinations. Two channels for alerts to reach me. Single points of failure in a one-person setup mean I am the backup.