[ About ]
I'm Ridham — I gravitate to the hard parts of software.
I'm a full-stack developer who spends most of my time where the hard problems live — real-time backends, event-driven architectures, and the AI systems that have to actually make a call. I like building the parts of an app that users never see but always feel.
That's meant building and shipping EnamDoc — a dental platform now in production with real users — solo, end to end, SEO and all. And before it: a real-time messaging engine on Socket.io, a NestJS transaction backend with queues and ACID guarantees, a poker agent that uses counterfactual regret minimization, and an ML platform that forecasts renewable energy from live weather. The throughline is the same: design the data and the failure modes first, then build up.
I work mostly in the TypeScript and Python ecosystems — Next.js, NestJS, React on top; Postgres, Redis, RabbitMQ, Prisma, and Docker underneath. When something needs to think, that's where TensorFlow, Gemini, and a bit of game theory come in.
[ How I work ]
Four things I keep coming back to.
The backend is the product
The polish people feel — instant, reliable, never-loses-your-data — is usually a backend decision. I design the data layer and the failure modes first.
Ship it, then prove it
A project isn't done until it's deployed and someone can click it. Eight of mine are live right now, not screenshots in a README.
Decisions, not just CRUD
The work I care about most is systems that decide — game-theory agents, ML forecasts, LLM features wired into real flows.
Boring where it counts
ACID transactions, queues, indexes, caches. Unglamorous primitives, used well, are what hold up when traffic shows up.