TL;DR: I joined Mergathon expecting to contribute to open source, but I walked away with much more than that. From leading the development of the Mergathon Dashboard to collaborating with an amazing community, this journey taught me teamwork, leadership, and why open source is much more than just writing code.

How It All Started

When I first joined Mergathon, I thought it would be just another open-source event where I’d contribute a few pull requests, learn something new, and move on.

I couldn’t have been more wrong.

Mergathon became one of the most memorable experiences of my journey as a developer.

One of the biggest opportunities I got was leading the development of the Mergathon Dashboard, a platform that tracked team rankings, contributions, and event statistics in real time.

It all started with a simple discussion. We decided on the tech stack, created a repository, divided the work, and slowly started turning ideas into reality.

At that moment, I had no idea that this project would become one of my favorite open source experiences.

Building Together

The best part of Mergathon wasn’t the dashboard.

It was the people.

Developers from different backgrounds came together with one common goal: building something useful for the community.

Everyone was ready to help.

Someone picked up an issue.

Someone fixed a bug.

Someone reviewed a pull request.

Someone suggested a better approach.

There was never a feeling of competition within the team.

Instead, it always felt like,

“Let’s build this together."

That is when I truly understood what open source is all about.

More Than Just Writing Code

Of course, the journey wasn’t perfect.

There were deployment issues.

There were GitHub API challenges.

Sometimes the leaderboard wasn’t updating correctly.

Sometimes fixing one bug introduced another one.

There were moments when things didn’t go as planned, but nobody gave up.

Every problem became a team discussion.

Every challenge became an opportunity to learn.

Looking back, those debugging sessions are some of my favorite memories because they taught me much more than any tutorial ever could.

Watching the Dashboard Come Alive

One of the happiest moments was watching people actually use the dashboard.

Participants kept refreshing it to check their team’s rankings.

People shared feedback, reported issues, requested features, and celebrated every update.

For the first time, I wasn’t just building a project for my resume.

I was building something that an entire community relied on during the event.

That feeling is difficult to describe.

It was incredibly rewarding.

Analytics Dashboard

The analytics page became one of my favorite parts of the project. Watching contribution trends, comparing team scores, and seeing all the activity visualized made the dashboard feel alive. It wasn’t just displaying numbers anymore it was telling the story of the entire event.

My Amazing Team

Along with building the dashboard, I was also part of Team LGTM.

Balancing dashboard development while reviewing pull requests and contributing to the event wasn’t always easy.

There were busy days, late nights, and lots of discussions.

But there was never a moment when I felt alone.

My teammates, mentors, and every contributor were always there to help.

Every suggestion improved the project.

Every review made the code better.

Every discussion taught me something new.

Looking back, I genuinely feel lucky to have worked with such an amazing group of people.

Lessons I’ll Always Remember

Mergathon taught me many technical skills, but the biggest lessons were beyond coding.

• Communication is just as important as writing good code.
• Leadership isn’t about doing everything yourself, it’s about helping everyone contribute.
• Asking questions is completely okay.
• Great software is built by teams, not individuals.
• Open source is about learning together and growing together.

These are lessons I’ll carry with me throughout my career.

Looking Back

When the event finally came to an end, the chat was filled with congratulations, appreciation, jokes, and messages from people saying they were genuinely sad it was over.

Honestly…

I felt exactly the same.

It didn’t feel like the end of a competition.

It felt like saying goodbye to a wonderful community.

Today, when I think about Mergathon, I don’t first remember the pull requests or the commits.

I remember the conversations.

The teamwork.

The excitement after every deployment.

The late-night debugging sessions.

The encouragement from teammates.

And the joy of building something meaningful together.

Final Thoughts

Mergathon gave me much more than technical experience.

It gave me confidence.

It gave me leadership experience.

It gave me friendships.

Most importantly, it showed me what the open source community truly stands for.

A huge thank you to every mentor, teammate, contributor, and organizer who made this experience unforgettable.

This journey reminded me that the best projects aren’t remembered because of the technologies behind them.

They’re remembered because of the people who built them together.

Thank you, Mergathon & CircuitVerse Team.