Building things for the web, from the interface to the infrastructure.
Hi, I'm Adith. I write code for the browser, the server, and the infrastructure underneath it. I'm drawn to the parts of a project where the frontend decisions start having backend consequences that's usually where the interesting problems are.
My defaults are React, Next.js, and Node. But I'll go wherever the problem is. The rest is better shown than explained in My portfolio.
What I'm learning, written down.
This blog is a byproduct of how I learn. I watch videos, read docs, fall down rabbit holes — and the ones that stick end up as notes in Obsidian. Some of those notes grew long enough to become posts.
The posts are technical but I'm not a technical writer. I used AI to help shape the content and generate the illustrations — and I think that's fine to say out loud. If something here helps a concept click that wasn't clicking before, that's the whole point.
How I Work
Velocity
Planning has diminishing returns. The fastest way to find out if an idea works is to build a version of it that people can actually click.
Clarity
The hardest part of engineering is keeping things simple. I reach for standard tools and obvious architectures so the focus stays on the product, not the plumbing.
Craft
Calling it a craft isn't about sounding artistic. It’s just admitting that there is always a smarter way to build something, and you have to actually put in the hours to learn it.
Available for new opportunities
I am currently looking for my next role. If you're building something interesting and need someone who cares deeply about design and execution, let's talk.