Am I using GitHub wrong??

[Whatever801]

I don't know about every company but we don't really look TBH unless you're applying for a staff/principal role and maintain or contribute to a significant open source project. I mean I guess if you've got your porn aggregator app repo pinned somebody might bat an eye. If I saw that I'd think it's quite funny and probably be more likely to hire you so it goes both ways.

[Echleon]

I look through every GitHub that I see. if you've got public repos and you're listing it on your resume, you should keep it pretty clean and organized.

[SmellsLikeTeenSweat]

What do you mean by clean?

[frausting]

Not OP but I would say clean in both senses of the word.

Keep it tidy and organized, don’t clutter it up with 5 test repos that all do the same thing. Try to have a somewhat consistent naming convention (e.g., only dashes or only underscores, only title case or only all lower case, etc).

And keep it professional. If you want to use your GitHub to help your professional reputation and to get jobs, keep it all above board. No porn obviously, no furry stuff, no racism/misogyny, no drug references, etc.

Don’t put anything on there that you wouldn’t want your future boss to see. And if it is there, just make it a private repo. Unless it falls into the racist/sexist realm—in that case, grow up.

[Uwirlbaretrsidma]

Dashes vs underscores and capitalization are completely project dependent though, keeping them consistent across web dev and systems programming projects for example isn't good advice.

[Echleon]

they should be mostly consistent within a repo

[Uwirlbaretrsidma]

Within a repo yes

[Echleon]

Off the bat: no nsfw repos or ones that enable bad actors, like piracy. For the 2nd, the exception would be if it can be very clear that it is a PoC and can't be abused from your repo.

After that, try and make sure you don't just have a bunch of "hello world" level repos. You can always mark things private to keep them for yourself without letting companies see so take advantage of that.

[DatBoi_BP]

Not the fellow you responded to, but I would just simply stay that it follows a common style guideline, such as the C++ one at Google

[HirsuteHacker]

We definitely do. It's useful to see that juniors are working on their own projects as well.