Notes from the workbench — short writing on backend systems, offline-first architecture, multi-tenant SaaS, and mobile.
Building a point-of-sale for shops on unreliable networks taught me that sync conflicts are a product decision — not something you bolt on later.
On a school-management platform, every tenant shares the same code and infrastructure but must never see each other's data. Tenancy is a discipline you enforce at every layer.
Shipping the same product to a Next.js web app, a React Native app, and a Flutter app at once forces a clarity about where the logic actually lives.
Modules, providers, guards — the framework hands you a lot. Here's the small subset I keep returning to across production APIs.
Most of the reliability people chase with microservices, they can get from a monolith and an honest queue. The work was always asynchronous — the queue just admits it.
A short note on building a career from Kotli, Azad Kashmir — where the connection drops more than it should, and why that turned out to be an advantage.
