Hear me out. Before you start another tutorial project, why not make an open source contribution?

I’m a hiring manager, and I review tons of resumes, GitHubs, portfolios every day. I’ve seen every version of Tic-Tac-Toe, Spotify Clone, Twitter Clone, Reddit clone you can imagine.While those are *ok* for developing some pattern matching skills (i.e. implementing an existing design), they really don’t stand out to anyone. Especially becasuse everyone does the same project.So why not do something thatStands out a lot moreIs much more educationalHas a positive impact on the fieldProbably because it’s hard. Sometimes PRs never get merged in. It takes a lot more communication, you have to discuss implementations and wait for code reviews.BUT that’s what every day as a software engineer is like. And it’s worthwile to make an effort!Common issuesI don’t know where to get startedI’ve tried and had a bad experienceI’m excluding the “I don’t have time to code free” because I’m explicitly talking about people who are already spending their spare time doing tutorials / self learning.Number 1 is pretty easy to resolve. Lots of resources available.Number 2 is harder. Sometimes there are really toxic people in the OS community. I’ve had a lot of contributions rejected (and told I was stupid for trying). To avoid this I usually:Look for repos with less than 200 stars (usually the more popular, the less beginner friendly)Communicate. Respond to an open issue. Open a new one if it hasn’t been address. Solicit feedback, and get maintainer buy-in before slinging out code.​Some resourcesMaking your first contribution: https://ift.tt/zxhRguQ first issues: https://ift.tt/pmCX8LA issues: https://ift.tt/lopeQIU contributors welcome: https://ift.tt/BmR3UCJ wanted: https://ift.tt/tO01MIe via /r/webdev https://ift.tt/GNEFqfV