Clarity
I'd rather ship a 50-line module the next person can read than a 15-line one only I can.
About
Senior full-stack engineer based in Pune. I work on React, Next.js, and TypeScript systems for products that need to scale past v1.
A little context
I'm based in Pune, and most of my work has involved building products that need to work through real complexity, not just look good in ideal conditions. That's probably why I've always been drawn to things that stay clear and useful as they grow.
What keeps me interested is the judgment around the work: what to simplify, what to optimize, what to leave alone, and what's actually worth building well.
A short version of how I grew into the kind of engineer I am now.
Started with a straightforward interest in building for the web, then got pulled deeper into the systems behind them. The more real product work I did, the more I cared about structure, maintainability, and the decisions that only show up once complexity arrives.
Over time I moved from shipping features to thinking about architecture, performance, and how products hold up after release. That's still the part of engineering I enjoy most.
I'd rather ship a 50-line module the next person can read than a 15-line one only I can.
Code that still makes sense six months and three feature pivots later.
I do my best work when I can think about the product, not just the ticket in front of me.
Self-hosted setups, IR blasters, side projects — most of what I learn comes from tinkering.
Software, like good design, should feel considered. I notice when it doesn't.
A few things that keep showing up outside the day job.
I like understanding the systems I use, not just consuming them.
Small experiments are usually where I learn fastest.
Playing drums is one of the better ways I get out of my head.
Some of the best resets are offline.
Especially if you care about strong engineering judgment, clear systems, and shipping work you can stand behind.