CSCareerQuestions

988 readers

2 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 2 years ago

MODERATORS

ericjmorey

odium

Do you use your personal Github as a portfolio when applying for jobs, or instead a self-hosted VCS (whether Git or otherwise)? (lemm.ee)

submitted 3 months ago by [email protected] to c/cs_career_questions

8 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] MajorHavoc 11 points 3 months ago (1 children)

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.

[–] ericjmorey 1 points 2 months ago (1 children)

Would you take note of someone using git compatible version control tools like, Jujutsu, Sapling, Gitless or Breezy? Or an entirely different hosting and version control setup like Pijul, Fossil, or DARCS? (Sapling and Breezy can be setup and used without git-based infrastructure as well)

My hunch is this is generally a negative signal for hiring managers because it's too far from standard practice in their world and could indicate someone who is too contrarian.

Anyway, I've tried all of these at various times and there's a lot I like about each and some I think are overall improvements over git. But git has so much momentum that people are very reluctant to try something even if it can smooth out the rough edges of git and git workflows.

[–] MajorHavoc 4 points 2 months ago* (last edited 2 months ago)

Those are all a signs of a curious mind, which is a big plus. There's also signs of not being a team player, and my job is to build a team.

So it all depends how the candidate communicates themselves.

The sweet spot is finding a new team member who is sure they'll convince my team to change tools, but is committed to embracing our current tools until they win over the rest of the team.