How it began
At first, I did not think of myself as a developer. I was just a student who liked seeing websites and wanted to understand how they worked. HTML was the first language that made sense to me because it gave structure to a page. CSS made the page look better. JavaScript made it feel alive. That combination was exciting because I could see the result immediately in the browser.
Learning from Nepal meant I had to be practical. I could not afford to wait for a perfect setup or a perfect course. I started with free resources, small notes, and a lot of testing in the browser. That taught me to appreciate simple tools and to build confidence from actual practice instead of from theory alone.
Why I began building projects
Reading tutorials is useful, but I learned much faster when I built things. A calculator, a Tic Tac Toe game, and a typing test are not huge apps, but they forced me to solve real problems. I had to think about buttons, logic, layout, and how to make the page feel smooth. Those projects gave me feedback that plain reading never could.
Each project also gave me a reason to improve. If I wanted a game to work well, I had to understand event handling. If I wanted the page to look professional, I had to improve my CSS. The project itself became the teacher. That is why I still value small builds so much.
The hard parts of learning
There were days when the code did not work and I did not know why. Sometimes the problem was a small typo. Sometimes I misunderstood the logic. Sometimes I was tired and did not focus enough. Those moments were frustrating, but they taught me persistence. I also learned that debugging is not a sign of failure. It is part of the process.
Another challenge was staying consistent while balancing other responsibilities. Like many students, I had to learn in short sessions. That meant I had to value quality over quantity. Even 30 focused minutes could move a project forward if I used the time properly.
What changed as I improved
As I kept building, I started seeing patterns. I learned to plan before coding. I learned to break a page into sections. I learned to test small pieces before adding more features. These habits made me more confident, because the work felt less random and more manageable.
I also realized that learning web development is not only about becoming “good at code.” It is about learning how to think clearly, solve small problems one step at a time, and keep improving after each attempt. That mindset has helped me beyond programming too.
My goals from here
I want to keep improving my frontend skills and build projects that are genuinely useful for students like me. I also want to write more clearly about what I learn so other beginners in Nepal can follow the same path with less confusion. If my projects and blog posts can help even a few learners feel more confident, that will be worth the effort.
For me, web development is not just a hobby. It is a way to create, learn, and grow from where I am. That is why I keep going back to the keyboard and the browser. Every small project is another step forward.