Curiosity,
put to work.

I started with curiosity. Building gave it direction.

At first, it was the possibility that drew me in: a few lines of code could become a page someone could use. That interest gradually became a habit of exploring how websites and software actually work. I began paying attention not only to what appears on a screen, but to the decisions underneath it—the structure of an interface, the logic behind an action, the data moving through a flow, and the way separate parts communicate.

That is also how I approach problems. If something breaks, replacing it or working around it is not always the answer. I investigate what went wrong, read documentation, compare approaches, test a fix, and keep going until I understand more than I did at the start. The process can take time, but I value the understanding it leaves behind. I bring the same care to finished work: check the details, revisit the experience, and distinguish what genuinely works from what still needs work.

Projects have given that curiosity somewhere practical to go. With Hire-Nepal, I explored the flow of a recruitment platform for job seekers and employers. With Prometheus X, I have been working on the software side of an environmental-monitoring system connected to physical hardware built by my teammate. They are different challenges, but both push me to think beyond a single screen and consider how a complete experience should behave.

I am still learning, and I would rather be honest about that than pretend to know everything. Recognition at project showcases has encouraged me, but it is the work behind each result that matters most: researching, collaborating, testing, and refining. I want to keep building clearer interfaces, stronger foundations, and more useful projects. The aim is not simply to finish something; it is to understand it well enough to make the next thing better.

I still start with questions. Now, I have a way to follow them: build, learn, repair, and improve.