My Journey in Open Source: 3 Years of Contributions

Three years ago, I stepped into open source with a simple mindset. I just wanted to improve my skills and see how real projects were built. At the time, I was used to building on my own, controlling everything from structure to logic. Open source was different. It forced me into an environment where I had to understand systems I did not create and contribute without breaking what already existed.

At the beginning, it was not easy. Reading other people’s code felt confusing. Every project had its own structure, naming style, and way of solving problems. I could not just jump in and start coding. I had to slow down, understand the system, and respect the existing architecture. That alone changed how I approach development.

One of the biggest lessons I learned early was patience. You cannot rush contributions. You need to understand the problem, read documentation, follow discussions, and sometimes wait for feedback. It is not like personal projects where you decide everything. You are part of a larger system, and your work has to align with it.

As I continued, I started to see improvement in how I think. I became better at reading code, understanding patterns, and spotting issues quickly. I also became more disciplined. Writing code for open source is different because other developers will review it. That pushes you to write cleaner, more structured, and more intentional code.

Collaboration is another thing that shaped my journey. Open source exposed me to different developers with different perspectives. Sometimes you agree, sometimes you do not, but you learn to communicate, explain your reasoning, and accept better approaches when necessary. That experience is something you cannot get from working alone.

Over time, I moved from small contributions to more meaningful ones. Fixing bugs turned into improving features, and improving features turned into understanding entire systems. That growth did not happen overnight, but it came from consistent effort and willingness to learn.

Open source also gave me confidence. Knowing that your code is part of something used by others changes your mindset. It makes you more careful, but also more confident in your ability to solve real problems. You start to trust your thinking and your decisions more.

Looking back at these three years, I can say open source played a major role in my development as an engineer. It improved my code quality, strengthened my problem solving skills, and exposed me to real world collaboration.

It also changed how I see development. It is no longer just about building projects for myself or clients. It is about contributing to systems, improving tools, and being part of something bigger.

The journey is still ongoing, but one thing is clear. Open source is not just something I do on the side. It is part of how I grow, how I learn, and how I continue to evolve as a developer.