this post was submitted on 03 Nov 2024
22 points (95.8% liked)
CSCareerQuestions
770 readers
12 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
What do you mean by documentation projects?
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.
That does sound a little dumb but maybe they were trying to create their own resource like awesome-lists or something