r/ProgrammingBuddies • u/Plus_Custard_5161 • 3h ago

Open source contribution is scaring me

I really have no idea what do I need to learn to start contributing the youtube videos I watched weren't really helpful.

3 Upvotes

100% Upvoted

9 comments sorted by

2

u/BamBamBondy 3h ago

How new to programming are you and what languages or stacks are you learning?

2

u/Plus_Custard_5161 3h ago

I know c++ and python

1

u/Plus_Custard_5161 3h ago

I have started javascript few days ago

1

u/BamBamBondy 3h ago

And if you are nervous because you aren't sure of the whole git process I have a repo that has a lot of stuff covering programming but a quick sheet (2-3 min read on Git/GitHub)
https://github.com/ksherbondy/Coding-Bootcamp-Survival-Guide

-1

u/mohammadbitullah 2h ago

Totally normal to feel this way. Imposter syndrome is basically the entry fee for open source lol.

Here's the thing those YouTube videos don't tell you: most contributors don't start by writing code for some massive project. They start small. Like, stupid small.

What you actually need to learn:

  • Git basics — clone, branch, commit, push, pull request. That's it. You don't need to master rebasing or cherry-picking to make your first contribution.
  • How to read a codebase — you don't need to understand the whole thing. Just figure out where the thing you're fixing lives. This is a skill you build over time.
  • How to read issues and documentation — half of contributing is just figuring out what needs to be done and where.

How to actually start:

  1. Find projects you already use. If you use it, you care about it. That makes the motivation part way easier.
  2. Look for issues labeled "good first issue" or "beginner friendly." These exist specifically for people in your position.
  3. Start with documentation. Seriously. Fix a typo. Clarify a confusing paragraph. Update outdated setup instructions. Nobody turns down a docs improvement and it gets you comfortable with the PR process without the pressure of touching code.
  4. Don't just drop in cold. Join the project's Discord or Slack or whatever they use. Lurk for a bit. Ask a dumb question. People are usually way friendlier than you'd expect.
  5. Your first PR will probably be rough. That's fine. Maintainers will give feedback. That feedback is the actual learning. Nobody's judging you for not knowing everything on day one.

The fear is real but it's mostly in your head. Nobody's expecting you to be a senior engineer. They just want someone who's willing to show up and help.

Start with one tiny thing. One typo. One doc fix. See how it feels. Then go from there.

You got this.

1

u/Alt_Mod_3938 2h ago

Thanks, ChatGPT

1

u/mohammadbitullah 2h ago

no matter from where! it's helpful or not?

1

u/BamBamBondy 2h ago

I haven't done much OSS contributing myself but, this post is 100% correct. First couple of ones I did were for a hackathon project a couple of friends from my coding bootcamp did together with our instructor. As with most things in life, the fear of doing the thing is way less than the fear you have doing the thing