DEV Community

Discussion on: My love-hate relationship with side-projects

Collapse
 
dabrorius profile image
Filip Defar • Edited

I would argue that having commits in an open source project is even better for your CV. First, it proves that you are able to solve real problems on a big project. Just linking to the list of your commits on a specific project should explain pretty well what part you are responsible for. For example Here's my small list of contributions to dev.to. If that's not enough, you can easily add a list of points describing what exactly you did.

The problem with adding side-project to your CV is that they get stale. You learn new things and you are not so proud of the way you solved something in there. Libraries get outdated, you might have built a great app with Rails 3 few years ago but now that version 5 is out is it really relevant to show it any more? You also need to host them somewhere.

Great thing about OS projects is that you can jump in when you have time available and then not work on them for years, but your contributions are recorded and will be valuable on your CV for a very long time.

Collapse
 
mxoliver profile image
Oliver

This is super helpful advice thank you