[{"data":1,"prerenderedAt":223},["ShallowReactive",2],{"page-en-\u002Fposts\u002Fyou-should-start-contribute-to-open-source":3},{"id":4,"title":5,"body":6,"description":211,"extension":212,"meta":213,"navigation":219,"path":210,"seo":220,"stem":221,"__hash__":222},"content_en\u002Fposts\u002Fyou-should-start-contribute-to-open-source.md","You should start contribute to open-source",{"type":7,"value":8},"minimark",[9,17,26,29,52,55,60,63,66,70,77,80,108,111,115,122,125,151,154,157,161,170,187,197,201,204],[10,11,13],"h1",{"id":12},"",[14,15],"binding",{"value":16},"title",[18,19,20,21,25],"p",{},"If you are good developer, but looking for an opportunity to grow professionaly, you ",[22,23,24],"strong",{},"should start contribute to open-source",". And the reason goes beyond benefiting the community — it's much more beneficial for you directly.",[18,27,28],{},"For a long time I was really interested in contributing, but I both underestimated the value I'd get from contributions and overestimated the complexity of the process. In this article I want to touch on both of these themes and maybe make you reconsider your perspective on OSS.",[18,30,31,32,39,40,45,46,51],{},"I'm proud to tell you that since the beginning of 2026 I've already made 10+ contributions, and even landed in the top 30 contributors in ",[33,34,38],"a",{"href":35,"rel":36},"https:\u002F\u002Freka-ui.com\u002F",[37],"nofollow","Reka UI"," — the core library for ",[33,41,44],{"href":42,"rel":43},"https:\u002F\u002Fui.nuxt.com\u002F",[37],"NuxtUI"," and ",[33,47,50],{"href":48,"rel":49},"https:\u002F\u002Fwww.shadcn-vue.com\u002F",[37],"shadcn-vue","!",[53,54],"hr",{},[56,57,59],"h2",{"id":58},"the-barrier","The barrier",[18,61,62],{},"For a long time, the idea of contributing felt out of reach. Maintainers are smart and professional — what could I possibly offer? On top of that — working full-time left only evenings, it's not common to contribute in Russia, so nobody around me had ever done it, and the process itself was a mystery. Should you just pick an open issue? Go through the whole project hunting for bugs?",[18,64,65],{},"I tried different approaches and found one that worked for me, so I want to share it with you.",[56,67,69],{"id":68},"the-playbook","The playbook",[18,71,72,73,76],{},"The key mindset shift was simple - yet hard to find: ",[22,74,75],{},"stop treating third-party bugs as your app's problem",".",[18,78,79],{},"Here's the workflow that made me understand how I could contribute:",[81,82,83,90,96,102],"ol",{},[84,85,86,89],"li",{},[22,87,88],{},"Split bugs into levels."," When something breaks, ask: is this your code or a dependency? It seems obvious, but think about how often you wrote workarounds for your app when the bug actually came from third-party.",[84,91,92,95],{},[22,93,94],{},"Dig into the source."," If the bug is from a third-party — open the source and trace it. Most bugs are easier to find than you'd expect.",[84,97,98,101],{},[22,99,100],{},"Solve first, then ask."," Come up with a fix and THEN open an issue asking if you can submit a PR. This order was key for me — the fear of taking on responsibility and failing was real. Knowing I had already found a fix made it much easier to step up.",[84,103,104,107],{},[22,105,106],{},"Protect your deadlines."," If you're worried about timelines at work (since you can't control when your PR gets merged) — create a workaround in your codebase anyway and add a TODO linking to the issue to track the upstream fix.",[18,109,110],{},"Your first contribution doesn't need to be massive. A missing translation, an unexported type, a docs typo — it's enough to get familiar with the workflow: forking, branching, opening PRs, responding to reviews, etc.",[56,112,114],{"id":113},"the-benefits","The benefits",[18,116,117,118,121],{},"So why do I think that you ",[22,119,120],{},"should contribute","?",[18,123,124],{},"As I said before — contributing is one of the rare cases where I underestimated the value I actually got. Every contribution delivers value in three directions at once:",[81,126,127,133,139],{},[84,128,129,132],{},[22,130,131],{},"Your product."," That bug you fixed upstream? It's now fixed for your project too — properly, not with a workaround. Your codebase gets cleaner, and you stop carrying technical debt that isn't yours.",[84,134,135,138],{},[22,136,137],{},"The community."," Every fix, every improvement, every translation helps thousands of developers who depend on the same library. Your one PR might save hundreds of people from writing the same workaround you did.",[84,140,141,144,145,150],{},[22,142,143],{},"Yourself."," You ",[33,146,149],{"href":147,"rel":148},"https:\u002F\u002Fmedium.com\u002F@mohitsingh3406\u002Fwhy-reading-code-is-more-important-than-writing-it-30c01a489375",[37],"read"," code written by experienced developers. You get reviews from people who think differently than your team. You learn to write code that strangers can understand, to communicate in PRs, to think about edge cases that don't exist in your own project.",[18,152,153],{},"On top of that, contributing can become a really good networking tool and source of job opportunities. Although the direct impact of contributions on your job offers is overrated — the network you can build through them is not.",[18,155,156],{},"All of these are exactly the traits that separate good developers from great ones. Think about any programmer you admire — chances are, they're an open-source contributor. I think that's not a coincidence — OSS contributions aren't a consequence of being great, but a cause.",[56,158,160],{"id":159},"the-controversy","The controversy",[18,162,163,164,169],{},"There's also an opposite position, which is well explained here: ",[33,165,168],{"href":166,"rel":167},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=5nY_cy8zcO4",[37],"Don't Contribute to Open Source",". You may notice that my article title is the straight opposite of that video — and that was deliberate. That kind of position was actually gatekeeping me from trying to contribute and grow professionally.",[18,171,172,173,176,177,182,183,186],{},"While I mostly don't agree with this position, I still ",[22,174,175],{},"highly"," recommend watching it, as I totally agree that situations like ",[33,178,181],{"href":179,"rel":180},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=YFkeOBqfQBw",[37],"Node.js README spam"," ",[22,184,185],{},"SHOULD NOT"," happen. I also understand the reason for gatekeeping, but I think it should be balanced and not too aggressive.",[18,188,189,190,193,194,76],{},"But let me make it clear — while you ",[22,191,192],{},"should start contribute to open source",", you also ",[22,195,196],{},"must be respectful and responsible for your actions",[56,198,200],{"id":199},"conclusion","Conclusion",[18,202,203],{},"If you've been thinking about contributing to open source but haven't started yet — you definitely should try. It could become both a growth opportunity and a rewarding experience. As for me — I'll definitely continue to contribute when I get the chance and free time.",[18,205,206,207,76],{},"Basically, that's why if you want to grow professionally you ",[208,209,24],"prose-a",{"target":12,"href":210},"\u002Fposts\u002Fyou-should-start-contribute-to-open-source","How I made first contribution — and why you should too","md",{"date":214,"duration":215,"toc":216,"tags":217},"2026-04-03 00:00:00 UTC","5 min",false,[218],"dev",true,{"title":5,"description":211},"posts\u002Fyou-should-start-contribute-to-open-source","uhSZ-huLZi18FYc-HAKVTnKW1CroGKbeWBCHCYfd9l4",1775217711150]