Free and Open Source Software

17937 readers

152 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

Gaywallet@beehaw.org

alyaza@beehaw.org

How do I know when I'm good enough at coding to solve issues/ commit code related changes on open source projects? (lemm.ee)

submitted 1 year ago* (last edited 1 year ago) by wtry@lemm.ee to c/foss@beehaw.org

16 comments fedilink hide all child comments

I program in C and python, and even good first issue problems seem like I have to be Dennis Ritchie himself to solve them. How do I know when I'm ready to solve and commit to projects?

you are viewing a single comment's thread
view the rest of the comments

[–] heeplr@feddit.de 7 points 1 year ago (1 children)

Rather if they get merged without edits.

I've seen even minor changes without flawed technique or style being discussed and changed for days before getting merged.

But it's also an excellent way to learn from pros. If the PR is worth it, they will spend the time for review and work with you until you fixed everything.

[–] Anticorp@lemmy.ml 8 points 1 year ago (1 children)

Eh, excellent code still gets discussed. Your approach might be unique and they haven't thought of it before. Or you may have perfectly suitable code, but it doesn't consider other parts of the project that you're not familiar with. Discussion isn't an indication of bad code, unless the only thing being discussed are mistakes.

[–] DmMacniel@feddit.de 2 points 1 year ago

That would be amazing, when your submission cause to improve the entire code base quality!