As a hiring manager of developers:
- If a candidate puts a link to public source code anywhere in their Resume, it’s the first thing I read.
- I see a lot of GitHub, of course.
- I consider GitLab, Codeberg, or even BitBucket to be a mild bonus. Hosting code history somewhere unusual implies some awareness of Git’s portability.
I’m personally still on GitHub, but planning to migrate my portfolio to somewhere with an open source back end over the next few years.
Selfhosting is a hobby for me, and as such I am constantly experimenting in “production.” It would be unwise to link to a page that can and will go down any moment.
You can do what I do and just have a branch for the GitHub pages bit, and just point GitHub pages at that branch instead of main to have a consistent webpage that you can rebase/merge into as you test things to make sure they’re safe
My job is almost entirely public on GitHub. It is in my resume and the next time I use my resume I hope folks read it. Lots of folks won’t but they probably don’t value my particular set of skills.
I think the usual wisdom is most jobs won’t care.
Resume building is the only reason I put anything on github.
Codeberg is my main Git host for now, but I also have GitHub and GitLab accounts. Unfortunately, I do not have the means to afford a cheap VPS, or self-host it locally.
