Blog
Writing
Offline-first architecture, software ownership, and the reliability habits I picked up from five years running systems where downtime had a real cost. Written from Pakistan, for people building where the network is never guaranteed.
You Don't Own That Software. You're Renting It.
Every CMS, PMS, and HRMS you pay for monthly leaves you a tenant in someone else's building. Offline-first isn't a feature choice — it's a property rights argument, and it's why I built Aafiyat the way I did.
Read articleOne-Time Payment vs. Monthly Subscription: The Math They Don't Show You
A Rs. 1,500/month subscription costs more than it looks once annual increases compound. Here's the three-year arithmetic, when subscriptions genuinely are the right call, and the exit cost nobody prices in.
Read articleYour App Shouldn't Need the Internet to Do Its Job
Offline-first isn't a feature — it's an architecture decision you make before you write your first route or component. How I build Aafiyat (Electron + SQLite) and the Nankana Home Care PWA to write locally first and sync in the background.
Read articleWhy I Build Software That Works When the World Doesn't
After 5+ years running mission-critical systems, I learned that reliable software must degrade gracefully, write locally first, and assume the network will vanish. Here's how it shapes Aafiyat and every project I build.
Read articleWhy I Build Offline-First
The network is the one thing you can't control. Here's why I design software that assumes it will disappear — and the three rules I follow on every project.
Read articleWhat Operating Mission-Critical Systems Taught Me About Software
Five years running systems where failure has a cost changed how I write code — and what I think 'reliable' means. Four principles I now apply to everything I build.
Read article