Too many Github repositories bad?

2 years ago by cherrycode to c/cs_career_questions

I'm still in my learning phase and I make many small projects as I learn. Is putting all of them on Github a good idea, if I want to put it on my resume in the future, or would having too many repositories on Github a bad thing?

tatterdemalion 12 points 2 years ago

Not necessarily. Just make sure the best projects are pinned or listed on your resume. Nobody has time to crawl through your entire GitHub anyway.

save

path: 0 13237819, hotness: undefined, score: 12, children: 0

MajorHavoc 11 points 2 years ago

Repeating what others have said, and adding a bit:

it's fine to have a bunch of repositories.
"pin" the ones you would most like to talk about in a job interview
"archive" projects that you're completely done with
be aware that pinned repositories and whichever repository has the most recent activity is probably the ones that I - an interviewer - will pick to ask questions about.

save

path: 0 13240467, hotness: undefined, score: 11, children: 2

cherrycode 2 points 2 years ago

Do I archive every small project that I'm done with?
What would you do if I archived the repositories with the most recent activity?

save

path: 0 13240467 13255631, hotness: undefined, score: 2, children: 1

MajorHavoc 3 points 2 years ago

Just archive projects that you don't want to talk about. That's pretty much all "archive" is for. It's a message to the world "I don't use this anymore. Don't ask me about it."

save

path: 0 13240467 13255631 13256619, hotness: undefined, score: 3, children: 0

quixotic120 6 points 2 years ago

save

path: 0 13238142, hotness: undefined, score: 6, children: 2

cherrycode 1 point 2 years ago

The commits on the 2nd account would have a different name and email right?

save

path: 0 13238142 13255639, hotness: undefined, score: 1, children: 1

quixotic120 1 point 2 years ago

save

path: 0 13238142 13255639 13262896, hotness: undefined, score: 1, children: 0

bluGill 5 points 2 years ago

They won't look until you have captured their attention and are trying to decide you vs someone else. unless it is an open source job nobody else will have a github account.

make sure nothing illegal to ask in an interview is there. I don't want to know you are black/white/married/have kids/or what ever. those can only hurt as I'm not supposed to know and I feel cheated when I find out and that works against you.

save

path: 0 13241757, hotness: undefined, score: 5, children: 0

lemmyng 4 points 2 years ago

A repo per project is not necessarily bad. However, don't create five dozen documentation projects, each of which is just a list of references. That's padding, and it'll be really obvious and annoying.

save

path: 0 13238060, hotness: undefined, score: 4, children: 3

cherrycode 3 points 2 years ago

What do you mean by documentation projects?

save

path: 0 13238060 13239185, hotness: undefined, score: 3, children: 2

lemmyng 5 points 2 years ago

I've interviewed a candidate that created dozens of GH projects, each one just being a list of tools for various topics. So they'd have "Programming tools", "Security", "Databases", etc. They may have thought that on the surface it would show them as a well-rounded candidate, but if you dug into it, it was just that - a set of lists. Even AI generated slop that gets churned out by the dozens these days has more content than those projects did. Even worse, when asked about their experience with the tools, the candidate couldn't give a useful response. It was like asking about the Donner Party and getting an answer about birthday parties.

save

path: 0 13238060 13239185 13239580, hotness: undefined, score: 5, children: 1

cherrycode 3 points 2 years ago

That does sound a little dumb but maybe they were trying to create their own resource like awesome-lists or something

save

path: 0 13238060 13239185 13239580 13255671, hotness: undefined, score: 3, children: 0

Rules/Guidelines

Related Communities

Credits

Rules/Guidelines

Related Communities

Credits