When I first started learning programming, my motivation was simple: I wanted to create things. Writing code felt powerful because it allowed me to turn ideas into something visible, functional, and useful. At that stage, I was fascinated by the practical side of development—web applications, automation scripts, APIs, and tools that solved immediate problems.
Over time, however, something changed. The more I built, the more I realized that behind every application there are deeper layers of thought: algorithms, system design, optimization, logic, intelligence, and the structure of computation itself. I started becoming just as interested in the foundations as I was in the final product.
From building projects to asking better questions
Projects gave me confidence, but they also gave me questions. When I worked on automation, I began wondering how systems could become more adaptive. When I explored AI-driven workflows, I became curious about how machines represent information, reason under constraints, and support human decision-making. When I built software for real use cases, I started thinking beyond implementation and more about efficiency, reliability, and long-term design.
For me, research is not a departure from development. It is the next deeper layer of the same curiosity.
Why research feels meaningful to me
I admire software engineering because it rewards clarity, discipline, and execution. But I am equally drawn to research because it rewards patience, depth, and original thought. Research is where we move from using known solutions to exploring unknown territory. That idea excites me.
The bridge between engineering and inquiry
One reason this path feels right for me is that I do not see industry and research as opposites. In fact, I think my software development background strengthens my future research ambitions. Building applications has taught me how real systems behave outside of theory. It has taught me about constraints, trade-offs, messy data, changing requirements, and the importance of designing for actual people.
At the same time, research offers the kind of intellectual challenge that keeps me growing. It pushes me to move from “How do I build this?” to questions like “How can this be improved fundamentally?”, “What assumptions does this system rely on?”, and “What is still unsolved here?”
What I hope to explore long term
My long-term vision is to keep building a strong engineering foundation while moving steadily toward deeper computer science inquiry. I am especially interested in areas where intelligent systems, software design, and rigorous thinking intersect. Whether that eventually takes shape through advanced study, applied research, or research-oriented engineering roles, the direction feels clear to me.
What I want my work to reflect
I want my work to reflect both practicality and depth. I want to be someone who can build useful systems today while also contributing to the ideas that shape the next generation of computing tomorrow.
In the beginning, programming felt exciting because it gave me the ability to create. Today, computer science research feels meaningful because it gives me a reason to keep asking better questions. That is why I see it not as a distant dream, but as the direction I am intentionally growing toward.