Pragmatic Systems Architecture, Zero-Fluff Engineering.
The story of how a small cyber cafe in central India became the testing ground for distributed web platforms, zero-compute client architectures, and enterprise engineering leadership.
From the Cyber Cafe Counter to Distributed Production Systems
My engineering trajectory did not begin in a Silicon Valley accelerator or an ivory-tower research lab. It started behind the counter of a busy cyber cafe and photocopy shop in Narmadapuram, Madhya Pradesh. Every single day, hundreds of ordinary citizens (students applying for competitive entrance exams, farmers registering government land records, and small business owners filing compliance forms) crowded the shop needing digital documents.
The tools available at the time were terrible: bloated desktop photo editors that crashed on low-spec hardware, web tools that required users to upload sensitive personal Aadhaar cards and photographs to unknown remote servers, and slow dial-up internet connections that choked on multi-megabyte image transfers.
That daily operational bottleneck instilled in me an uncompromising engineering instinct: software must be fast, resilient under low bandwidth, zero-cost where possible, and completely protective of user privacy. That insight eventually led to the creation of Photocopywala.in, which today serves more than 7,000 daily active users across India entirely inside the client's browser using HTML5 Canvas and WebAssembly, incurring practically zero monthly server compute costs and never storing a single byte of private user paperwork on an external cloud server.
Architectural Philosophy: Simplicity as a Hard Requirement
In over a decade of architecting web solutions, ranging from multi-warehouse enterprise ERP engines to international B2B platforms and high-conversion SaaS, I have observed that the single greatest source of engineering failure is not technical inadequacy, but unnecessary architectural complexity.
Teams routinely adopt distributed microservice meshes, un-indexed polyglot persistence, and premature orchestration for systems handling fewer than 100 requests per second. The result is always catastrophic: ballooning AWS invoices, cascading failure cascades, impossible local debugging environments, and team burnout.
// Four Immutable Architectural Laws
If computation can execute safely and deterministically on the user's client CPU via WebAssembly or Canvas, keep it off the server. It eliminates cloud latency, eliminates infrastructure costs, and eliminates data leak vectors.
Enforce strict domain boundaries, typed module contracts, and clean hexagonal architecture within a single unified deployable until organizational team size genuinely demands independent deployment lifecycles.
Runtime errors are design errors. Strict TypeScript across client, server actions, and database schemas ensures compile-time invariants and guarantees reproducible software across team boundaries.
Performance is not an afterthought or a nice-to-have badge. It directly correlates with business conversion, user retention, and algorithmic search visibility. Sub-500ms TTFB and 0 cumulative layout shift are baseline standards.
Shrimo Innovations & Engineering Mentorship
In September 2024, I formally incorporated Shrimo Innovations Private Limited in Narmadapuram to serve as the corporate entity for our proprietary product laboratory and high-end software consulting practice. Under Shrimo, we develop independent micro-SaaS ventures such as DigitingCard, OutbidGrow, and DekhoBiz, while providing high-stakes technical advisory to venture-backed startups and established regional enterprises.
Beyond shipping software, mentorship remains a cornerstone of my professional work. I have directly mentored over 100 junior and mid-level engineers in modern full-stack development, transitioning them from tutorial hell into confident systems thinkers capable of architecting production-grade MERN and Next.js applications with automated testing and continuous deployment.