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

[-] jarfil@beehaw.org 5 points 1 year ago* (last edited 1 year ago)

How do I know when I'm ready to solve and commit to projects?

There are a few ways:

You notice a problem, write some code, compile/run it, and it works. 🎉
Download a project with some tests, set up the testing environment, do as per point 1, run the tests and keep fixing your code until they don't fail anymore. 🎉
Do as per point 1, submit the PR... and many people will tell you whether you've missed something. Depending on their character, they might be helpful, ignore you, or rarely be assholes. YMMV. 🎭
Fork the project. Now you're in control, so proceed as per point 1. To make your life easier, write some tests, set up a testing environment, make it easy for others to replicate, document stuff, both for you and for others, describe the general architecture to have a high level view of it, and so on. 🎉

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

Gaywallet@beehaw.org

alyaza@beehaw.org