8 ms·

> well too bad I work 15 hours a day in this tech company that has private git repos Same. I've been in the industry for nearly 25 years and have written hundr

• bastardoperator 4y ago
  If you want to play the game: https://github.com/artiebits/fake-git-history https://github.com/artiebits/fake-git-history
  • kube-system 4y ago
    If I am considering a candidate enough to look at their GitHub, I will actually look at the content. If someone was actually trying to pass this off as relevant work, I’d disqualify them for being dishonest. They’d be 1000x better off by having no GitHub history.
    • bastardoperator 4y ago
      Not if it's in a private repo... you won't be looking at anything. Are you going to outright reject a candidate because you can't see contributions to their current employers private org/repo? I believe this is the point the poster is trying to drive home. You can't see their contributions because they're private.
      • kube-system 4y ago
        If you commit only to private repos then you shouldn’t be linking to your GitHub, as this article also says. Resumes are for communication. Communicate! Tell the reader what you do, and demonstrate it as much as you can. Everyone knows that private repos are a thing, that’s okay. This can be articulated.
        • CBarkleyU 4y ago
          I've never linked to my GitHub, yet it sometimes still comes up in interviews.
        • bastardoperator 4y ago
          The article says verbatim "Don’t include a link to your GitHub link if it’s empty." yet you're giving 1000x (your words) credence to an empty profile versus someone working privately. Private contributions show up on the graph, you just can't see the content of the commit. So it's not empty and to your point it can be articulated. Sounds like you just want to see some examples of work, just ask for that, but that's not a resume.
          • deleted 4y ago
            [deleted]
          • kube-system 4y ago
            “A commit graph and nothing else” is approximately equivalent to empty as far as I am concerned. If I clicked such a link on a resume, I’d say “wtf am I supposed to be looking at here?” If your repos are private, just tell me they’re private. It is well known that many engineers can’t share their work. It isn’t a requirement. But if you do share your GitHub, make sure it adds value to your resume and doesn’t detract from it.
            • vsareto 4y ago
              >doesn’t detract from it I don't know if that's truly obvious from a candidate's POV, especially if they don't know the person reviewing their stuff
        • Arainach 4y ago
          My Github has projects I have worked on in the past. Most of them are stable and don't need anything more than a few npm dependency updates a year. Linking to it to see these projects is useful to the kind of company that wants to see some small things I've built. If fake contributions to a private repo will tick a box somewhere, so be it.
      • lolinder 4y ago
        If it's in a private repo, there's no point. Your GitHub stats exclude private repos when viewed by anyone besides you.
        • fsociety 4y ago
          You can set it so it shows contribution stats from private repos. Also companies with healthy attitudes to devs can allow their enterprise GitHub instance to transfer contribution stats to dev’s personal GitHub accounts.
          • bastardoperator 4y ago
            ^this