Why I Contribute to Open Source — and Why It Matters for the Future of Software

Modern software would not exist in its current form without open-source contributions.

From the frameworks we build with to the infrastructure that powers global platforms, open source has become the backbone of the digital world.

Today, open source underpins the vast majority of modern software. Studies show that 96% of codebases include open-source components*, while more than 90% of companies—including the vast majority of Fortune 500 organisations—use open-source software** as part of their technology stack.

Technologies such as React, Next.js, Node.js, and Docker are not simply tools. They represent a global model where thousands of engineers collaborate to build, test, and improve software together.

For developers, contributing to open source is not just about sharing code. It is about strengthening the ecosystem that powers modern digital platforms.

Why Developers Contribute

Most developers begin their careers learning from open resources. Documentation, GitHub repositories, tutorials, and community guides often become the foundation for understanding new technologies.

Over the years I realised something important: the reason these resources exist is because someone decided to share their knowledge for free. That idea stayed with me. If open resources helped me grow as an engineer, the best way to give back was to contribute to the same ecosystem.

For me, contributing to open source started with writing technical content and sharing practical solutions to problems I encountered while building applications.

Like many engineers, I initially hesitated to publish anything. It’s easy to assume someone else knows more or has already written about the topic.

Three years later, the number of readers was more than 250,000 per year, proving something important — fear is often the only thing standing between people and progress.

Over time, what started as small contributions—writing guides, improving documentation, and sharing practical examples—became part of a larger effort to help developers understand how modern applications are built and deployed.

Open Collaboration Accelerates Innovation

Open source moves quickly because it’s not limited to one team, one company, or one perspective.

When a new framework, library, or tool is released, the community begins testing it immediately. Developers identify issues, suggest improvements, and build additional tools around it.

This collaborative cycle dramatically accelerates innovation. Features improve faster, bugs are identified earlier, and solutions emerge from a global network of developers working across companies and industries.

I’ve seen this first-hand. When my Docker examples for running Next.js applications were merged into the official repository, what started as a small contribution became part of the documentation developers use globally.

That’s the real power of open collaboration: individual contributions can scale far beyond their original intent.

Why Open Source Strengthens Quality Software

Open source doesn’t just accelerate innovation—it improves quality.

Because the code is public, it is reviewed, tested, and challenged by developers globally. Issues are identified faster, security vulnerabilities are discovered earlier, and improvements often happen far more quickly than in closed systems.

This transparency is one of the reasons organisations increasingly trust open technologies. Many of the platforms that power global digital services today are open-source projects maintained by large communities of contributors.

In many ways, the reliability of modern software depends on this collaborative model. 

What Developers Learn By Contributing 

Contributing to open projects also offers something developers cannot easily gain elsewhere: exposure to real production ecosystems.

When engineers contribute to open repositories, they learn how large systems are structured, how experienced developers approach architectural decisions, and how software evolves over time.

This kind of experience is difficult to replicate in tutorials or isolated learning environments. It comes from participating in real-world projects that thousands of developers rely on.

For many engineers, contributing becomes one of the most effective ways to grow—not just technically, but in how they think about building software.

Why Open Ecosystems Matter for Organisations 

The impact of open source goes far beyond the developer community.

Companies today increasingly build their digital platforms using open technologies because they offer flexibility, innovation, and access to global expertise.

Instead of building everything from scratch, organisations can adopt tools that are continuously improved by the wider community.

That shift allows teams to focus on what differentiates them—solving real customer problems—rather than rebuilding foundational technology.

Open ecosystems have become a fundamental part of how modern digital platforms are built.

And How You Can do the Same 

The important thing is that open-source contribution doesn’t have to start with something big. It can begin with a guide, an example, a documentation improvement, or sharing a practical lesson others can build on.

I’ve contributed to the open-source ecosystem through a combination of practical guides, real-world examples, and official documentation improvements. My work focuses mainly on helping developers understand how to take modern web applications—especially those built with React, Next.js, Angular, and Vue—and run them reliably in production using Docker.

One of my key contributions includes creating Docker-based examples for Next.js applications, which were later merged into the official Next.js repository maintained by Vercel. This allows developers worldwide to use production-ready container setups directly from the official documentation.

In addition, I’ve contributed to Docker’s official documentation by providing structured, beginner-friendly guides for containerizing React.js, Angular, Vue.js, Node.js, Next.js applications. Beyond that, I actively share knowledge through open-source repositories, technical articles, and community-driven content aimed at making complex topics simpler and more practical for everyday developers.

I also share what I learn as a speaker at international conferences and events, helping more developers engage with the ideas, tools, and practices shaping modern software.

What matters most is that none of these contributions started as something huge — just as something useful. That’s often how open source grows: one shared idea, one practical example, or one improvement at a time.