Reading this made me think about where the easiest place to contribute to OSS is. Either you build code to hook up two things where there is no existing hookup

Reading this made me think about where the easiest place to contribute to OSS is. Either you build code to hook up two things where there is no existing hookup (or do something someone else has done in a different language, framework, or you address a bug or add a feature to something you are familiar with. Occasionally there is low hanging fruit... like as I get better at languages, I can submit a pr for cleaner or more idiomatic code. But honestly, If you want to make OSS better, don't code, clean, format and add to documentation/comments/examples/distribution methods. Because often useful code lacks the documentation that tells you what it does and how to use it effectively. Often it doesn't provide a simple explanation of how to install, much less a way to install directly. The best way to get people interested in a project is to show how it can benefit them and make it easy to use. If you are just learning, then reading and interpreting code is a skill you need to build, because much of professional software development is about reading and understanding existing code.