More Than Code: The Humbling Lesson from My Second Open Source Contribution

September 7, 2025 (3mo ago)

Jump to FAQs

A maintainer reviewed my pull request and left a comment that stopped me in my tracks:

There are already a ctrl+tab implementation, if the ctrl+shift+[] is needed we can hook it up with the existing implementation which also has some ui.

Your PR is also messing with the current ctrl+tab stuff.

I paused and re-read the comment. Embarrassingly, I had no idea a Ctrl+Tab switcher even existed in the browser. I had been so focused on implementing my solution that I failed to fully explore the application's existing features.

I immediately tried it, and sure enough, pressing Ctrl+Tab brought up a neat UI for cycling through tabs. My implementation was not only redundant, but it also interfered with this established system.


The Real Value of Contributing

This experience was a powerful "Today I Learned" moment for me. But the lesson wasn't just about a keyboard shortcut. It was a stark reminder that contributing to open source is a dialogue, not a monologue.

My first contribution was a clean win, but this second attempt taught me something far more critical: the importance of understanding the existing landscape of a project before adding to it. It drove home the point that open source isn't just about writing code and pushing it into the world. It's about:

This journey is solidifying my belief that open source is one of the most effective ways to grow as a developer. You're exposed to different perspectives, forced to read and understand unfamiliar code, and you learn things about the world of software you simply wouldn't know otherwise.

My pull request may not have been merged as-is, but the knowledge I gained from the experience was worth so much more. Now, I'm closing my pull request.

Discuss this post:

Frequently Asked Questions

What was the issue with the second pull request?

The pull request implemented a new tab-switching shortcut (Cmd+Shift+[]) without realizing the project already had a similar, more advanced feature (Ctrl+Tab). The new code was redundant and conflicted with the existing system.

Is getting critical feedback on a pull request a bad thing?

No, constructive feedback is a positive and essential part of the open-source process. It's a valuable opportunity to learn about the project's codebase, discover features you didn't know about, and improve your skills as a collaborative developer.

What's the key lesson from this follow-up experience?

The key lesson is that contributing to open source is about more than just writing code. It's about learning, collaborating, and taking the time to understand the existing ecosystem of a project before adding to it. The feedback loop is a powerful tool for growth.