I don't see any reason to get rid of them. You may revisit these later, or want to remember how you solved a specific problem. Interviewers and recruiters aren't going to be digging deep into your GH graveyard to see if every commit you've ever made was a smash hit, they'll be scanning your featured, polished work.
Updating your READMEs is a great idea, but I think you only need to spend the time doing so for projects you'd specifically like the opportunity to talk more about with an interviewer.
Senior App Dev @ Acuity Brands Lighting | Co-Founder of https://ct3dao.io | President of https://NewHaven.IO | Maintainer of https://TechEnthusiastScholarship.com | https://HenryGives.Coffee
Location
New Haven, CT
Education
Computer Network & Information Security @ Champlain College
Update your READMEs if you think a potential employer might ask questions about certain repos.
What I did was keep everything that at least had a "version 1" completed. I made private most repos that were some kind of "follow along with the tutorial" or projects that I just kind of started then lost interest in. That way they're there if I ever want to revisit them, but my GitHub won't be full of projects that didn't yield some kind of result.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't see any reason to get rid of them. You may revisit these later, or want to remember how you solved a specific problem. Interviewers and recruiters aren't going to be digging deep into your GH graveyard to see if every commit you've ever made was a smash hit, they'll be scanning your featured, polished work.
Updating your READMEs is a great idea, but I think you only need to spend the time doing so for projects you'd specifically like the opportunity to talk more about with an interviewer.
That does make sense. Hopefully I'll push em down anyway with new projects.
README updates it is!
What Ben said. No reason to nuke stuff.
Update your READMEs if you think a potential employer might ask questions about certain repos.
What I did was keep everything that at least had a "version 1" completed. I made private most repos that were some kind of "follow along with the tutorial" or projects that I just kind of started then lost interest in. That way they're there if I ever want to revisit them, but my GitHub won't be full of projects that didn't yield some kind of result.