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

Free and Open Source Software

17926 readers
73 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
60
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
[โ€“] RandoCalrandian@kbin.social 5 points 1 year ago* (last edited 1 year ago) (1 children)

Every problem looks impossible until you see the solution, and then it was obvious the whole time.

The feeling never goes away, instead you do what some other commenters have suggested:

  • pick a project
  • get it building locally so you can fix something
  • pick a bug from the list
  • get to work. Understanding what to write means understanding what the solution is, which means understanding the problem and the scope of it, what parts you can fix and what not. This process is more akin to going on a nature hike than painting the view, but people always seem to assume coding is more like the latter.

Tbh, you will likely be able to eventually solve any bug, given time and effort. Reaching out to discord groups in the language or product domain when you have questions will speed the process up.

[โ€“] Pierre@beehaw.org 2 points 1 year ago

When choosing a bug, if you start with one that is possible to reproduce, it might help following the instructions to reproduce it while debugging the app and observe what happens. This can be a way to start understanding how it all runs. Bugs without context or hard to reproduce are usually more complicated and you might need a better knowledge of the code to have an idea of where to look.