Look beneath the surface.
I want to know what makes something work, not just how to make it work once.
A LITTLE ABOUT THE MIND BEHIND AR.DEV
It started
with a question.
How do things work? That simple question sparked my curiosity about technology. I didn't have a complete plan or all the resources I needed. I just wanted to understand more, and that curiosity eventually brought me here.
01 / THE BEGINNING
Curiosity came before code.
My interest in technology began with wanting to understand what happens behind the things we use. I was curious about how something designed on a screen could respond to a person, how different parts of a system worked together, and what made the whole thing possible.
In 2022, I started reading and scrolling through everything I could find about technology, and I decided to understand it in depth instead of staying on the surface.
Eventually, curiosity turned into experimentation. I began learning to code on a mobile phone, working with the tools I had rather than waiting for ideal conditions. In May 2024, I moved from a phone to a laptop, and my projects grew with the upgrade.
It wasn't always convenient. Limited resources made the beginning harder, and staying consistent with what I had available took effort. But the urge to understand how things worked kept bringing me back.
I learned that getting started doesn't require having everything figured out. Sometimes, it starts with asking a question and finding a way to explore the answer.
A PRINCIPLE I COME BACK TO
You don't need perfect conditions to begin. You need the curiosity to find a way.
A thought that continues to shape my approach.
02 / THE APPROACH
The details are part of the work.
Understanding how something works is only part of the experience for me. I also want to understand why it behaves the way it does, where it could be improved, and what might go unnoticed if I stop paying attention too early.
I tend to focus on the small corners of a project: the little features, interactions, and refinements that might not stand out immediately. Those details are where my curiosity often shows up in the work itself.
I want each part to feel considered, not merely present. That means looking beyond whether something works and paying attention to how it works, how it feels to use, and whether the smaller pieces fit together properly.
I'm still learning what good execution looks like, but I want to keep that instinct: look closer, question the obvious, and finish the details rather than overlooking them.
Notice the small things.
The experience is shaped by details that can be easy to overlook when rushing toward the finish.
Keep pushing further.
When I reach the edge of what I know, I want to use it as a starting point for learning something new.
03 / BEYOND THE SCREEN
A student, a reader, a listener.
I'm in the first year of my B.Tech in Computer Science and Engineering. College gives structure to what I've been learning on my own, and I want to build on that foundation.
Away from the keyboard, I read articles and books and listen to a lot of music. Both keep me curious and help me recharge.
Building the foundation.
Computer Science and Engineering adds theory to what I've learned by building.
Always something to learn.
Articles and books keep my curiosity fed between projects.
Music, in and out of the editor.
Something I genuinely love, and part of who I am beyond the code.
04 / WHAT COMES NEXT
Beyond what I know.
Beyond what I know.
Beyond what I've built.
For me, working beyond limits means a combination of things: not letting limited resources define what I can attempt, continuing to explore beyond my current knowledge, and eventually creating useful products that go further than individual websites.
I don't see learning as a checklist that ends when a technology is mastered. Each new understanding creates another question, another possibility, or another thing worth building.
I don't have every step of the future mapped out, and I don't think I need to. I'd rather keep building, pay attention to what each experience teaches me, and stay open to ideas I haven't discovered yet.
Right now, I'm looking for internships and open-source contributions where I can learn alongside experienced developers, and for individual dev projects where I can build something useful from start to finish. I usually reply within a day.