So I want to make a GitHub portfolio that I can show my potential employers.
What kind of projects would you put on GitHub for the employers to see? Any resume tips?
>>56252455
Nothing. Get a real degree.
For the few people I've hired/interviewed I basically looked for any code contributions that weren't shit. I don't remember what any of the projects that they had because I really didn't car. Any save the world bullshit would have been a red flag though because I want people who want to write software not people who are going to fuck my spot up
>>56252515
I'm new to this; what do you mean by "save the world bullshit"?
>>56253593
Not that guy, but I would guess people who only commit code of conduct and make readmes politically correct rather than actual cobtributions
>>56252455
Forget github
Find an open source project. Look up list of features people want/or project mgrs want to add.
Add them.
Debug said features when bugs come up.
Repeat until you're good. Show that to future employers if the open source project doesn't already hire you (orig how I got hired to postgresql)
I just upload half-finished shit and occasionally get around to finishing them. Also contribute bugfixes to random stuff that I use and find a problem I can fix in.
>>56253916
>working for free
>>56253926
>building a resume
>having zero education and zero work history
>adding features to programs you already use
you're already working for free when you apply to anybody these days "oh hai plz spend all weekend making this app..." wai what
>>56253916
>Show that to future employers
"Anon, I can't find that contribution on Github. I suspect you're lying about it".