I did not start my journey into software development with a clear plan.
Like many students, I initially thought becoming a software developer was mostly about learning programming languages, solving problems, and eventually getting a job. But the more I built, the more I realized that software development was much more than writing code. It was about being able to take an unclear problem, break it down, struggle with it, and keep going until something actually works.
My journey started during my Computer Science studies at Chandigarh Engineering College Jhanjeri. At first, I was simply trying to understand programming and web development. Gradually, I became fascinated by the fact that an idea in my head could become something people could actually interact with through a browser.
That curiosity pushed me toward web development.
I started working with JavaScript and React, and eventually moved into Next.js, TypeScript, Node.js, databases, authentication, APIs, and cloud deployment. Every new technology opened another door—and usually another problem.
One of the biggest lessons I learned was that building something locally is only the beginning.
I have spent countless hours staring at build errors, deployment failures, database connection problems, environment-variable issues, authentication errors, and cloud infrastructure that worked perfectly on my machine but refused to work somewhere else.
There were times when I felt completely stuck.
I remember working on projects where a single configuration issue could stop an entire deployment. I would trace logs, read documentation, change one thing, break another, and start again. Sometimes the solution was a tiny change hidden behind hours of debugging.
Those experiences were frustrating, but they changed the way I think.
I stopped seeing errors as signs that I was not good enough and started seeing them as part of the engineering process.
I also learned by building things that were far beyond what I initially felt comfortable with. I worked on websites, event registration systems, automated email workflows, full-stack applications, database-backed systems, cloud deployments, and experiments involving AI and automation.
Some projects were polished. Some were messy. Some taught me more because they failed.
And I became comfortable with that.
Another important part of my journey has been learning how to work with AI-assisted development. AI has made it possible for me to explore technologies much faster, but it has also taught me an important lesson,
"Generating code is easy but understanding what that code is doing, debugging it, and making the right engineering decisions is the real challenge."
I don't want to be someone who simply asks an AI to build things.
I want to become the engineer who understands the system well enough to know what should be built, why it should be built that way, and how to fix it when it inevitably breaks.
That mindset is still developing.
There have been periods when I struggled with confidence, felt behind other developers, or questioned whether I was learning fast enough. Looking at the amount of technology I still don't know can sometimes feel overwhelming.
But when I look back, I can also see how far I have come.
I went from trying to understand how a website works to thinking about frontend architecture, APIs, databases, authentication, deployment, performance, cloud infrastructure, and the complete lifecycle of an application.
I am still learning. In fact, that is one of the things I enjoy most about software development.
There is always another problem to solve.
Today, my goal is to become a strong software engineer who can build useful products from idea to production. I am particularly interested in modern web development with technologies such as React, Next.js, TypeScript, Node.js, and PostgreSQL, while continuing to deepen my understanding of system design, cloud infrastructure, and AI-powered applications.
I don't expect the journey ahead to be easy.
I've already learned that it won't be.
But that is also what makes it exciting.
I started this journey because I wanted to build things.
I want to continue it by becoming someone who can build them well.
