Writing
Notes on backend engineering, APIs, and the things I build when something I need doesn't exist yet.
- ·5 min read
I shipped instead of grinding
Three years of a BCA in a small city in Rajasthan. No internship, no referrals, no LeetCode streak. I built things that run in production instead — and I want to be honest about what that cost.
- ·5 min read
The agent is not the engineer
I built a metered API — sync protocol, billing webhooks, 116 tests — working with coding agents most of the way. The speed was real. So was everything it quietly got wrong.
- ·4 min read
Test the API, not the function
I have 116 tests on my API and almost no unit tests. That isn't laziness — it's the only way I've found to make a test suite that catches real bugs instead of guarding trivia.
- ·3 min read
Auth is the part you can't fake
Anyone can wire up a login form. The part that separates a real backend from a toy is what happens on every request after it.
- ·3 min read
Local-first, then sync
A workout app that stalls on the gym's terrible wifi is useless. So I built GymPlanner to treat the network as optional — and it made everything feel instant.
- ·2 min read
Why I built an exercise API nobody asked for
Every fitness app needs an exercise catalog. Almost none of them have a good one. So I built the API I kept wishing existed.