Software engineer · building on the web from Pune, India

Portfolio · LinkedIn · Twitter/X · Email

Most of what I make starts as curiosity and ends as something I actually use. Small tools compound — the throwaway script you wrote last year is somebody's daily driver today, sometimes your own. That's the part I keep coming back for.

• Typed, component-driven UIs — the kind where you can land in any file and understand it in a minute.
• Small sharp tools — plugins, extensions, CLIs, utilities that do one thing and get out of the way.
• End-to-end products where one person owns the seam between the API and the screen.

• POCs first, products second. New idea, new library, unfamiliar domain — I spin up a throwaway repo and kick the tires before it touches anything real. Half of them die there, and that's the point.
• Boring code over clever code. Small functions, real names, short files. If the next person needs a map to read it, I wrote too much.
• Narrow the problem before widening the solution. Most bugs and features get smaller once you look at them properly.
• AI as sparring partner, not autocomplete. I hand it tight context, push back when it's off, change my mind when it's right, and ask for a review pass before anything ships.
• Ship, then polish. A rough thing in someone's hands beats a perfect thing in my head.

Badminton, football, fantasy novels, manga, long sessions of whatever game has my attention, and getting out of the city when I can.