In an industry obsessed with titles, I find myself without a clean one, and I've stopped looking. Aneesh Sharma is early in a career that doesn't yet have edges. Backend systems, frontend interfaces, design, architecture: I move between them not out of confusion, but out of genuine curiosity about how things fit together.
The honest thesis is this:
"I don't know what kind of engineer I'll be in ten years. But I know I want to understand, deeply, carefully, not just how to ship, but why the abstractions we reach for are the ones we do."
Writing here is not about tutorials or trending frameworks. It is an act of thinking in public. I believe the best way to understand a concurrency model, a design pattern, or an architectural tradeoff is to try to explain it, and to sit with the discomfort of realizing you can't yet. That gap is where the real learning is.
Principles of Work
I approach software the way others approach language, with a suspicion of cleverness and a preference for clarity. The right abstraction is not the one that shows off what's possible, but the one that makes the next person's job obvious. I reach for Go when I want to think about structure. I reach for the browser when I want to think about people.
Depth over Velocity
Understanding something slowly is faster than misunderstanding it quickly.
Work Across the Stack
The best systems are built by people who've felt the weight of every layer they depend on.
This blog is a living document of a mind still being made. It will change as I do. If something here made you think differently about a problem, or made you feel less alone in not knowing, then it worked. Thank you for reading slowly.