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

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
[-] bet@lemm.ee 2 points 1 year ago

In the sense I think you're asking, never: contributing a fix or an improvement is never a one-and-done, fire it off and forget it edit. Each contribution is a request to open a dialog. Implicit in each pull request are multiple questions, perhaps including "is this a good idea", and "do you like this attempt to do it".

If the project maintainer who reviews your PR doesn't like it, they can expend the effort to try to explain why, and teach you. So try to make their job easier, by opening with a clear explanation of why you're doing it, and if what you did involved design decisions, why you chose as you did.

this post was submitted on 17 Sep 2023
68 points (100.0% liked)

Free and Open Source Software

17911 readers
72 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