3 ms·

People are scared you won't commit code and will do nothing. A long public commit history on GitHub is good and seems to do a lot. Also, once you have the job

People are scared you won't commit code and will do nothing. A long public commit history on GitHub is good and seems to do a lot. Also, once you have the job, keep the git active too. The good commit logs help you write invoices more accurately also and serve as a record.

kevin42 9y ago
I'm not sure that's always a positive. I'm not saying it should be this way, but there are very many companies and industries where a long open source development history won't be seen as a reflection of what the developer can do in a job. Not all companies are going to take an interest in GitHub history. I think the majority of development jobs are with companies that have a skepticism of their employees contributing to open source projects because they don't understand it and are worried about their IP being co-opted into open source.
- shortoncash 9y ago
  Oh, if I wasn't clear, I meant using git as a form of work record at your company. If you have a nice commit log, it's easy to point to your own productivity. I didn't mean keep committing to open source repos.
imhoguy 9y ago
Make sure your new workplace will benefit your GH investment and community too. The Github is overcrowded with mocked contributions just to boost resumes. I am not against open-source contributions and putting them on CV, but foremost they should be done not for fame but for community benefit. Also I laugh when closed-source only company asks for GH contributions but they don't contribute anything and don't let one to work on GH in paid time. That means you spend your evenings and time off to keep up with GH - only if your contracts permits that too.
- shortoncash 9y ago
  Great comment! I worked in a closed, secretive space for a long time. When I left the secretive space, I had no public "street credit" that would've helped me land remote work. I had to rely on referrals. I'm 100% certain public code and street credit would have made my potential clients more comfortable with me. Plus, having the benefits of having a long, extended public track record communicating with others would have helped too.

kevin42 9y ago

I'm not sure that's always a positive. I'm not saying it should be this way, but there are very many companies and industries where a long open source development history won't be seen as a reflection of what the developer can do in a job. Not all companies are going to take an interest in GitHub history. I think the majority of development jobs are with companies that have a skepticism of their employees contributing to open source projects because they don't understand it and are worried about their IP being co-opted into open source.

shortoncash 9y ago
Oh, if I wasn't clear, I meant using git as a form of work record at your company. If you have a nice commit log, it's easy to point to your own productivity. I didn't mean keep committing to open source repos.

imhoguy 9y ago

Make sure your new workplace will benefit your GH investment and community too. The Github is overcrowded with mocked contributions just to boost resumes. I am not against open-source contributions and putting them on CV, but foremost they should be done not for fame but for community benefit. Also I laugh when closed-source only company asks for GH contributions but they don't contribute anything and don't let one to work on GH in paid time. That means you spend your evenings and time off to keep up with GH - only if your contracts permits that too.

shortoncash 9y ago
Great comment! I worked in a closed, secretive space for a long time. When I left the secretive space, I had no public "street credit" that would've helped me land remote work. I had to rely on referrals. I'm 100% certain public code and street credit would have made my potential clients more comfortable with me. Plus, having the benefits of having a long, extended public track record communicating with others would have helped too.