I'm new to GitHub and I'm planning to create a repository for both commercial use and as a reference for potential employers during job applications. I'm torn because if I make it public, I'm worried about people stealing my code. On the other hand, if it's private, potential employers won't see my work. What do you all think? Any advice would be appreciated!
3 Answers
As a beginner, it’s probably best to start with a private repo. You can always make it public later once you’re more comfortable. This way, you can refine your code without worrying about it being picked apart.
Yeah, starting private is a smart move for newbies!
Let’s be honest here: most HR teams won’t even look at your GitHub. If a tech person does, they’ll likely scan for only a couple of minutes at most. Your work is valuable, but it’s likely not their primary focus. If you have a unique project, talk about it in interviews instead of worrying about visibility right now.
It’s refreshing to hear that! Thanks for your perspective!
That’s a good point! I’ve gotta let my work speak for itself in person.
Here's a useful rule to consider: most of the code you write isn’t as groundbreaking as you might think, so the odds of someone stealing it are pretty low. If you're working on a significant project with commercial intent, definitely keep it private. For smaller, personal projects, you can go public as long as you don’t share sensitive info. Remember, if HR is checking your repo, it’s likely for a big project, so you can mention it in interviews instead.
Thanks for the insight! I really appreciate the reassurance!
I agree with you, making smaller projects public can really help you get feedback.
That makes sense! It’ll give me the freedom to experiment without the pressure.