0+
Years shipping to production
0+
Enterprise apps, owned start to finish
0+
Daily operations across 17+ warehouses
0%
Uptime. Zero excuses.
Who I am
I started with code.
Then APIs. Then databases. Then integrations.
Then production.
10,000+ operations a day, 17+ warehouses. Without going down.
Real names on the other end — Zepto, Reliance, Nykaa, the Indian Army, Trent, Delhivery.
Lately: a streaming service, self-hosted from nothing.
A trust layer a modified app can't talk its way past.
This site is the same instinct, pointed somewhere new.
Currently
Software Development Engineer
Falcon Autotech Pvt Ltd
May 2024 – Present
I care more about what happens when things go wrong than when they go right.
01
Offline-first by default — a warehouse floor doesn't get downtime as an option.
02
A contract is a feature. Payload shape, status codes, error responses — product decisions, not implementation details.
03
Security built in from day one. Never bolted on after.
04
Data is architecture. Schema, queries, state — they shape behavior, not just storage.
05
If it's going to fail, I want to see it fail before someone else tells me.
06
I stay accountable past the handoff. Not someone else's problem once it ships.
Things I've actually debugged
Local Docker worked. The deployed VPS didn't.
Different network, different behavior. Deployment turns assumptions into evidence.
A stream played fine, then just stopped.
URLs expire. Rebuilt playback to re-resolve instead of dying.
Play Integrity kept failing — never the same way twice.
Isolated it variable by variable, on-device, until it held.
A modified APK could still call the backend.
Moved the trust decision server-side. The client doesn't get to decide.
A chat room works fine at 10 users. What about 10,000?
Did the read-amplification math by hand before trusting the default fanout.
Debugging was eating into delivery time.
Reusable logging, offline-first by default. 40% less time chasing failures.