3 ms·
This may be an unpopular opinion, but I've never understood why so many people recommend contributing to open-source projects if you are a CS student or beginne
by EnderMB 8y ago
This may be an unpopular opinion, but I've never understood why so many people recommend contributing to open-source projects if you are a CS student or beginner. It's a fantastic way to feel inadequate in your ability to write code. If you pick a large open-source project your skills may not be up to scratch to help out in any meaningful way. Even with smaller tasks, a lot of larger projects have enough structure in place to ensure that trusted developers are working on key parts of the project, so it's likely that getting involved will take a lot of effort.
There's definitely an argument for contributing to open source projects, but I'd recommend finding small utilities over big-name projects. These have their own dangers with contributors often abandoning projects, or ignoring issues/pr's, but it's a much easier way to get involved and get some open-source contribution cred on your CV/resume.
As others have said, the best approach would be to create your own project, and should things go well there maybe look into seeing if there are any now-defunct projects you like the look of that would consider handing the reins over to you to maintain.
One last option would be Google's Summer of Code. It's too late to join in for this year, but it may be worth it next year if you're serious about contributing to a big-name project. The acceptance rate isn't great (I applied three times and didn't get in once, but this was years ago), but given your niche interests you might be a perfect candidate for a handful of projects.