← Back to context

Comment by dmurray

5 years ago

You may have missed it, but the article screenshots a similar example where the spammer added "### Great Work" to the front of the README.

I’ve heard of people spamming readme commits to get their github graph green... I guess if an employer is tricked by something like this they are kinda asking for what they get.

  • That’s a failure of imagination and evidence of having never read the Git manual pages, because the GitHub contribution graph respects commit time (which you absolutely can override), and it’s a trivial hour-long project to write messages on it. I had greenscale pixel rendering of images on the contribution graph working in about an hour, most of which was figuring out the heuristics for quantity in each cell (hint: it’s not as complex as you think).

    I can’t understate the simplicity of doing it, and I’d be nervous about someone taking the other approach as indicative of their technical depth. Then again, they’re already spamming READMEs so it’s not as if it was a strong signal to start with.

    • It's pretty easy, but if I'm looking at your Github to look at your work I can't find anything if you've clobbered your true history with a message.

      I don't ever see that as a negative signal, but I do see it as a positive signal if I can just read your code, so if you write good code in public and you hide it, I can't find it.

      Of course, whether you care is up to you, but if I find solid code there I'm going to recommend skipping technical evaluation if you're considering working with me.

      1 reply →

  • Any employer that looks at an applicants activity graph in any serious way only deserves the kind of people they will get.

    Every employer worth working for will at least look at some actual code you've written, both in your own projects and in contributions to others.

    And even then an in-person interview should be able to offset any github activity or lack thereof.

Oh you're right! I was reading on my phone and bucketed that picture as a link to the other blog posts like the carousel at the bottom and mentally skipped it. My mistake!

  • Sorry about that carousel. I want to get rid of Disqus entirely (when I started the blog in 2012 they were not so icky). But, then I think about related yak-shaving, like moving off of Jekyll...

    • I’ve been down that rabbit hole myself. My blog is still running Jekyll but my comments are now on a self-hosted install of Commento. It works pretty well. For me the main feature is that it’s not Disqus, but another nice benefit is that comments support Markdown now!

    • It's all good. The error was mine. Disqus was, indeed, a great product back then. I didn't realize they added all this stuff now.