If someone had told me a year ago that I would spend hours reading documentation, debugging code, and genuinely enjoying the process of building software, I probably would not have believed them.
Computers always fascinated me, but programming felt like something meant for other people. It looked complicated, intimidating, and honestly, far beyond what I thought I was capable of. Websites especially seemed almost magical. I would open one in my browser and wonder how someone could possibly create something that looked so polished and interactive.
At some point, that curiosity became difficult to ignore.
I did not start with ambitious goals or a detailed roadmap. I simply wanted to understand what was happening behind the screen. That curiosity led me to HTML.
The first few days were surprisingly simple. I learned that a webpage was not magic at all. It was just a collection of tags, each with a purpose. A heading here, a paragraph there, an image placed carefully inside the right element. It was not glamorous, but every small thing I learned made websites feel a little less mysterious.
I still remember the excitement of creating my very first webpage. It was not beautiful. It was not responsive. It certainly was not something I would show the world. But it was mine.
That small success changed something. Instead of wondering how websites were built, I had started asking what else can I build?
As I kept learning, I realized coding was not really about memorizing syntax. It was about solving problems. Sometimes those problems were tiny, like a button refusing to align or an image refusing to load. Other times they were much bigger. Either way, every bug forced me to think differently.
There were days when nothing worked.
There were moments when a missing semicolon or a misplaced bracket would keep me stuck for hours. I questioned whether I was learning the right way, whether I was progressing fast enough, and whether I belonged in a field where everyone else seemed so much more experienced.
But every time I solved one of those problems, no matter how small, I became a little more confident than I had been the day before.
Without realizing it, I had stopped learning because I had to and started learning because I genuinely enjoyed it.
As I explored further, I discovered that software development was much larger than websites. Every application, every tool, every system people use every day begins as someone's idea and countless lines of code. That realization made me appreciate software engineering in a completely different way.
I started paying attention to how applications were designed, how interfaces felt, and how different technologies worked together. Building something was not just about making it functional anymore. It was about creating something that another person could actually use.
One thing that surprised me was how much there is to learn. Every answer seemed to lead to three more questions. At first, that felt overwhelming. Eventually, I began to see it differently. The fact that there is always something new to discover is what makes this field exciting.
Looking back, I do not think my journey began when I wrote my first line of HTML. It began much earlier, with a simple question: "How are websites made?"
That question led me into programming. Programming led me into software development. And software development slowly became something I wanted to build a future around.
I am still learning. There are countless technologies I have not explored, concepts I do not fully understand, and skills I hope to improve. But I no longer feel intimidated by that. Every developer starts somewhere, and every experienced engineer was once a beginner trying to understand their first webpage.
I do not know exactly where this journey will take me, but I do know why I want to continue it. Because there is something deeply satisfying about turning an idea into something real. And if a simple curiosity about websites could bring me this far, I am excited to see where the next question leads.
