When I first heard about the OSS.GG hackathon, I saw it as a perfect way to blend my love for open-source with the challenges of Hacktoberfest. Open-source events are always exciting, but OSS.GG felt especially unique. Not only was I working with awesome projects and learning new tools, but I was also part of a community rallying to build and improve open-source software together.

As I reflect on the past few weeks, I realize how much I’ve grown, both as a developer and as a contributor. Let me walk you through my journey at OSS.GG — from the thrill of fixing issues to the deep satisfaction of building templates and sharing knowledge.

Jumping In: Why OSS.GG Stood Out to Me

I’ve always been fascinated by open-source projects because they bring together a collective brainpower that’s just not possible anywhere else. There’s an unspoken thrill in finding issues, suggesting fixes, and knowing that someone out there will actually use your code to make their life easier. OSS.GG intrigued me from the start because it offered a structured way to contribute and provided specific side quests and challenges that added a sense of adventure to the process.

But more than that, OSS.GG allowed me to work with tools I had little prior experience with, like Unkey and Formbricks. Each project, whether big or small, felt like a piece of a much larger puzzle — and I couldn’t wait to start contributing.

The Journey Begins: My Contributions at OSS.GG

1. Fixing Bugs in the Twenty Repository

One of my first contributions was to Twenty, a repository with documentation and resources that were a bit tangled up. Some files in the twenty-side-quest directory contained leftover content from another project, which referenced a different Twitter account. It may seem like a small fix, but getting the documentation right is so important. Clean, accurate instructions are the backbone of a smooth developer experience.

The challenge: To make sure every single file referenced Twenty’s Twitter account accurately and was in sync with the project’s Notion documentation. It was a chance to focus on the less glamorous, yet super important part of open-source — maintaining clear and consistent documentation. This process showed me that even small contributions can have a ripple effect, especially when they enhance the readability and accuracy of a project.

2. Diving into Unkey’s Rate Limiting: My Favorite Side Quest

If there’s one skill that every developer should master, it’s understanding rate limiting. It’s the kind of problem that often flies under the radar until it doesn’t — and by then, it’s usually too late. OSS.GG offered me a challenge to integrate Unkey's rate limiting into different setups, and I was hooked.

Creating an Oak Server Template with Deno: I began with Deno, a runtime I hadn’t explored deeply before. Using Oak, I created a server that had two types of routes — one public, and another rate-limited. With Unkey, I set the rate limit to allow only two requests in a 30-second window on the /secret route, ensuring that users would get rate-limited if they exceeded the limit. It was a fun way to showcase Unkey's functionality and really brought to life the concept of throttling requests.

Hono Server with Cloudflare Workers: Next, I took the challenge up a notch by building a Hono server deployed on Cloudflare Workers. This time, setting up rate limiting for a distributed environment added an extra layer of complexity. Unkey handled the rate limiting flawlessly, and the experience opened my eyes to how rate limiting can be easily implemented in different environments.

Integrating Unkey’s Rate Limiter into CodeStash: This one was close to my heart. My project, CodeStash, features an AI-powered code explanation tool that users can activate with an "Explain this" button. Without proper rate limiting, this feature could easily become overloaded. By integrating Unkey’s rate limiter, I was able to control the load on this feature, making it a smoother experience for everyone. Writing a technical blog on the process helped me articulate the steps and solidify my understanding of API security.

These Unkey contributions were some of the most fulfilling parts of OSS.GG for me. They weren’t just technical tasks; they were opportunities to learn, experiment, and make tangible improvements to projects I care about.

3. Formbricks: Building for Feedback-Driven Development

Toward the end of the hackathon, I got the chance to work with Formbricks. CodeStash is all about sharing knowledge and empowering developers, so I wanted to understand how users felt about the AI explanations feature. Integrating Formbricks allowed me to gather this user feedback seamlessly, and it was eye-opening.

Writing a technical article about my Formbricks integration was both challenging and rewarding. I detailed the step-by-step process, from setting up Formbricks to embedding the surveys in CodeStash, and shared the insights I gained. This experience taught me the power of feedback-driven development and has inspired me to make it a core part of future projects.

What OSS.GG Taught Me

The Value of Small Fixes: Whether it’s fixing typos or adjusting references, small contributions matter. They’re often overlooked, but they’re the glue that holds projects together, making them accessible to more people.

The Importance of API Security: Rate limiting has become a core part of my development toolkit, thanks to Unkey. It’s not just about setting request limits; it’s about protecting resources and ensuring a reliable experience for everyone.

Feedback is Key: Formbricks reminded me how essential user feedback is. Even the best features need feedback loops to become truly great. This has reshaped my approach to development, pushing me to prioritize user experience and continuous improvement.

The Power of Community: Throughout OSS.GG, I was in touch with other contributors, exchanging ideas and troubleshooting together. It reminded me of the open-source ethos — we’re all here to make things better, and there’s immense value in sharing knowledge along the way.

Final Thoughts: Why You Should Dive into Open Source
OSS.GG was much more than a contest for me; it was an invitation to connect with the open-source community and give back. Every contribution, no matter how small, taught me something valuable. And in return, I felt a deep sense of belonging in a global community of passionate developers.

If you’ve been considering open-source contributions but haven’t taken the plunge yet, I can’t recommend it enough. Start with something small. The challenges may feel intimidating at first, but each success brings a huge sense of accomplishment. Whether it’s fixing a bug, creating templates, or writing documentation, every contribution counts — and the community will always be there to support you.

Looking Ahead

As OSS.GG wraps up, I’m already excited about future hackathons and contributions. This journey has strengthened my resolve to keep building and sharing, and I hope to inspire others to join the world of open-source as well. To all the maintainers, contributors, and organizers at OSS.GG — thank you for making this such an unforgettable experience.

Here’s to many more contributions, collaborations, and community-driven projects. Open source is for everyone, and I’m grateful to be part of it.