CSCareerQuestions

950 readers

1 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Follow the programming.dev site rules
Please only post questions here, not articles to avoid the discussion being about the article instead of the question

Related Communities

[email protected] - a general programming community
[email protected] - general question community
[email protected] - for questions targeted towards experienced developers

Credits

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

[email protected]

Too many Github repositories bad? (lemmy.ml)

submitted 1 week ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 11 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] [email protected] 1 points 1 week ago (1 children)

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?

[–] [email protected] 2 points 1 week ago* (last edited 1 week 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."