5 ms·

That's the same Catch-22 situation I'm in. I'm trying to find work and eveyrwhere I look it's "We want to look at your Github profile and open source contributi

by Khao 13y ago

That's the same Catch-22 situation I'm in. I'm trying to find work and eveyrwhere I look it's "We want to look at your Github profile and open source contribution!" Fuck. I don't have any of those because I mostly code at work and if I do stuff at home it's very unprofessional and only for personal use. I don't have time to contribute to open source and frankly I don't even want to but that doesn't make me less of a good programmer. I love my job but when I'm at home, I have other hobbies and interests.

city41 13y ago
The reality is most of your competition does have side projects. It's an unfortunate reality of this industry. I've been on both sides of the equation and it's definitely true that having an active github and StackOverflow profile is very helpful :-/
leknarf 13y ago
I ask applicants for a Github link, but it's not nearly as big a deal as you might think. Some people have interesting work on github. Others don't, but have something else to show instead. I'll look at whatever a candidate sends over (within reason). And open source contributions are a lot easier to make than you might expect, when you consider non-code contributions. Opening an issue on github for an open-source library is a great signal. A well-written bug ticket tells me: 1 - You write enough unique software to encounter bugs in other developers' work (i.e., you're not just duplicating the same CRUD work everyone else is) 2 - You understand how to identify common tasks in your application that should be delegated to a library (and don't try to just re-write everything yourself) 3 - The details in the bug ticket show that you understand what information is relevant to solving a problem and can communicate with other developers. Those sorts of contributions should be possible in most work environments, as part of your normal job responsibilities.
- hackula1 13y ago
  Submitting an issue is often much more appreciated as a project maintainer than a big code dump pull request.
quaffapint 13y ago
Agreed - I can't show my full time job stuff and my at home stuff is for a little side money to pay my bills and not open source. I don't want to just throw random stuff up there.

by Khao 13y ago

city41 13y ago

The reality is most of your competition does have side projects. It's an unfortunate reality of this industry. I've been on both sides of the equation and it's definitely true that having an active github and StackOverflow profile is very helpful :-/

leknarf 13y ago

I ask applicants for a Github link, but it's not nearly as big a deal as you might think. Some people have interesting work on github. Others don't, but have something else to show instead. I'll look at whatever a candidate sends over (within reason). And open source contributions are a lot easier to make than you might expect, when you consider non-code contributions. Opening an issue on github for an open-source library is a great signal. A well-written bug ticket tells me: 1 - You write enough unique software to encounter bugs in other developers' work (i.e., you're not just duplicating the same CRUD work everyone else is) 2 - You understand how to identify common tasks in your application that should be delegated to a library (and don't try to just re-write everything yourself) 3 - The details in the bug ticket show that you understand what information is relevant to solving a problem and can communicate with other developers. Those sorts of contributions should be possible in most work environments, as part of your normal job responsibilities.

hackula1 13y ago
Submitting an issue is often much more appreciated as a project maintainer than a big code dump pull request.

quaffapint 13y ago

Agreed - I can't show my full time job stuff and my at home stuff is for a little side money to pay my bills and not open source. I don't want to just throw random stuff up there.