Ideas

Things I think about

A loose collection of ideas that shape how I build software and think about the world it runs in. Nothing here is a finished article — just thinking out loud.

---

Offline-first is a respect choice

Most apps treat the network as a constant. It isn't. When I built Aafiyat for clinics, the defining constraint wasn't a feature — it was a power cut. A doctor mid-consultation can't pause because the router blinked. Offline-first isn't a technical fad. It's a respect choice. The person on the other side of the screen shouldn't pay for our cloud bill or our uptime graphs.

Reliability is a human property

Five years operating government systems at Punjab Police taught me something the tech world often misses: reliability is a human property, not just a technical one. A tool that confuses the tired operator at 2 a.m. will produce bad data no matter how elegant the backend. Audit trails beat cleverness. Reversible actions beat speed. Graceful degradation beats loud failure.

Build for the worst network day

The network is the one thing you can't control. I design software that assumes it will disappear. Local state is the source of truth — remote is a replica. Sync in the background, never in the critical path. Conflicts are flagged, not silently resolved. Build for the worst network day, not the demo day.

Quiet software

Less animation, more clarity. Code and copy should make sense to someone else in six months — including future me. Small, sharp tools. Solve the real problem, then stop building. The best software is the kind you forget is there.

The public sector needs better tools

Government systems affect real lives — clinics, citizen services, law enforcement. Too often they're built for procurement, not for people. There's an enormous opportunity for developers who care about the craft to build systems that actually serve the communities they're meant for.

Local data, local trust

When your data lives on someone else's server, you're trusting their uptime, their policies, and their incentives. Local-first architecture flips that — your data is yours. Sync is a courtesy, not a crutch. The local database is the system.

---