Re:Ask HN: What do recruiters look for in a GitHub profile?
by chillacy on Sunday March 17, 2019 @07:48PM
(#19417572)
Tell us in the readme if you make it public. You gotta think, who is reading this? That goes beyond documentation to code itself and any communication you do.
[ Parent
| on HN ]
Re:Ask HN: What do recruiters look for in a GitHub profile?
by godelski on Sunday March 17, 2019 @08:31PM
(#19417779)
Repositories are public for a lot of reasons, a lot of which are not "I want to show this off to a potential employer". Let me give some good reasons, that's not an exhaustive list.
- It is the default.
- Free private repos are new and no one is going back and making things private.
- If you are working with someone it is many times easier to make it public.
- You want to share code with someone, public is easier than making them a collaborator.
Honestly I don't think a lot of people, if any, are reading the stuff I have on GitHub.
Re:Ask HN: What do recruiters look for in a GitHub profile?
by seba_dos1 on Sunday March 17, 2019 @10:08PM
(#19418200)
I put my things public on GPL out of principle, because there are some people playing those games, so I want to provide all necessary freedoms to them - even if nobody is actually interested in exercising those freedoms, because well, those are shitty jam games.