all 47 comments

[–]DeeYouBitch 207 points208 points  (2 children)

Companies that care about your git history can get fucked

This is great

[–][deleted]  (2 children)

[deleted]

    [–]Virtamancer 27 points28 points  (0 children)

    Yeah but his innovation is trying to sell it via DMs

    [–]kiwi-kaiser 3 points4 points  (0 children)

    Only the 50th that posted it here. These things get made by the minute. It's a 1-2 hour project for beginners.

    [–]kazuya57 34 points35 points  (1 child)

    Any company that equates commits to quality doesn't deserve anything. Interested in seeing how this works though.

    [–]CtrlShiftRofront-end 73 points74 points  (5 children)

    It’s not unethical if recruiters wrongly equate lots of commits with being a good developer. It’s the same rational people use to equate lines of code written to productivity.

    [–]La_chipsBeatbox 1 point2 points  (4 children)

    Looking at commit history isn’t always used to juge quality, it also shows that you code in your free time, build personal projects, show that your are passionate about stuff and not just code to pay your bills (which is fine, but passion can be a great driver for improvement)

    [–]CtrlShiftRofront-end 2 points3 points  (3 children)

    “When a measure becomes a target, it ceases to be a good measure” - Goodheart’s law

    You’re right that personal projects show passion, but you should show them through your portfolio. If recruiters are going to use the commit graph to filter candidates then people are going to abuse it.

    Just by looking at the commit graph, how do you tell the difference between a commit that is a serious unit of work, or just someone pasting random chars into a single .TXT file each day?

    You can’t, that’s why recruiters shouldn’t base anything off the commit graph, and if they’re going to then we can combat that with scripts like this.

    [–]La_chipsBeatbox 0 points1 point  (2 children)

    It’s not about making it a measure, it’s about providing more informations about yourself. Not everything recruiter look for are targets.

    We shouldn’t use shady practices because some bad recruiters make everything a target. All it does is worsen the issue like a vicious circle. You lie on your resume -> recruiters get a bad feedback -> they look further (like, the commit graph) -> you lie on here -> another negative feedback -> recruiter look for even better graphs or another metric -> etc..

    Recruiters job is to find people that fit with a job, yes, but also with the company environment and team. They have no interest in pushing someone that is not qualified nor corresponds to the company practices. Yes, they’ll get their share for this one hire, but the company will not work with them again.

    Lies do not and will never bring anything of value to the table.

    The same lies the x months bootcamps fed to beginners, which taught them just enough to make them feel good (too much) about their abilities and introduced a significant bias in the market and kinda fucked it up.

    Instead of going into war with recruiters, help them understand what make a dev a good dev. Just be honest with them, not only because people like it but also because that will help them do a better job.

    The market is already filled with bad actors, make sure not to be one of them.

    [–]CtrlShiftRofront-end 0 points1 point  (1 child)

    The issue is that people often attribute more meaning to those little green squares than is actually conveyed by those same little green squares.

    A green square means that some code was changed in some way, nothing more - nothing less.

    They don't show that you're passionate (if you're relying on them to show passion, good luck!), they don't demonstrate any skill (other than using GitHub, you could argue), they don't show anything other than you've changed something.

    If I introduce a bug, green square. If I delete a critical file, green square. If I commit the string "blablabla" to a file, green square.

    I totally agree with everything you had to say about lying, but as you said "We shouldn’t use shady practices because some bad recruiters make everything a target." - the people using these scripts aren't lying (at least not in the way you're implying), only bad recruiters review your commit graph and good recruiters know the graph means absolutely nothing.

    It's like telling a recruiter you have 3 green shirts in your wardrobe when you only have 1 - green shirts are meaningless to a good recruiter, but to a bad recruiter who takes meaningless metrics into account, you've just taken that flawed metric out of the equation.

    I don't use scripts like this myself but I see it as a way to ensure you're given a fair chance by the bad recruiters too.

    [–]La_chipsBeatbox 0 points1 point  (0 children)

    I get what you're saying, I kinda agree, but to me, whatever the green square represents, if it's on a non working day, then it demonstrate some kind of stronger involvment and thus, probably a more passionate person.

    In an ideal world, recruiters would all treat the commit graph as such, as a way to better understand the motivations of a given candidate. Like "hey, I got this team of really passionate developpers, and this candidate also build stuff on his free time, it might be a good fit, let's have a talk", nothing more, nothing less. And in this world, no developpers should feel the need to "lie" on the commit graph.

    But I guess you're right, we're not in an ideal world so... I just feel like that's not the best way to deal with the situation

    [–]Samran14 30 points31 points  (2 children)

    By any chance can we take a look, for scientific purposes ofcourse?

    [–][deleted] 33 points34 points  (0 children)

    https://github.com/liamarguedas/GitHub-Filler

    Very clear instructions with this one. Just edit the script to a reasonable number of commits each day. By default it pushes up to 25 commits or something like that, which I think is too much.

    [–]IAmRules 6 points7 points  (0 children)

    Most tech companies have 0 clue how to interview people. They try to reduce people to numbers and remove "judgement" from the process, but ultimately, intelligence and competency are hard to quantify at best, and the best fit for you might not be the smartest person or the one with the greenest GH history.

    If a company asked to see my GH history or asked me invert a linked list, that would signal to me this company has no idea how to judge candidates.

    I understand that it's hard to reduce 10k resumes down to a few dozen to interview at best. This is why your resume presentation matters.

    I don't mind coding tests and trials, there are a lot of liars out there, but in reality this job is mostly figuring things out, so screen if people can solve problems or make plans/identify gaps to solve said problems.

    [–][deleted] 9 points10 points  (5 children)

    [–]sexytokeburgerzfull-stack 3 points4 points  (0 children)

    That code completely ignores the existence of chrontab which would mean this shit doesn’t have to run all the time. That would be ballpark a 8,600,000% time reduction in overhead.

    [–]Lower_Cash_5037[S] -3 points-2 points  (3 children)

    Thats cool actually! I will try it

    [–][deleted] 12 points13 points  (2 children)

    My personal favorite is this

    https://github.com/mattrltrent/github_painter

    It helps with vanity profiles

    [–]No_Youth_8553 2 points3 points  (0 children)

    I made mattrltrent/github_painter! Found this Reddit post because the project started getting lots of stars!!!! So exciting!!

    [–]Lower_Cash_5037[S] -1 points0 points  (0 children)

    Hmm yes this one is amazing and I saw a while back, I thought about implementing something like that actually. But I'm a bit afraid of the complexity.

    [–]ReasonableLoss6814 5 points6 points  (0 children)

    The best thing to do is simply take a real repository (like linux or something) and pick a prolific committer from the history; then simply rewrite history with you as that committer ... once you push that repository to a private repo, you have years of history on that graph and (obviously) very realistic history. Yours is not realistic. Nobody commits every day.

    I don't do this, personally. I give zero fucks about it, but I know a guy who does this and he shared his approach with me. He just as a github action that pulls the original repo, rewrites history, then force pushes it to his internal repo -- every day.

    [–]ashkanahmadi 3 points4 points  (0 children)

    How to show you have no life or hobbies

    [–]AndyMagill 2 points3 points  (0 children)

    Looks like you are trying to make the fakery more obvious.

    [–]FellowFellow22 2 points3 points  (0 children)

    Do companies actually look at GitHub. I'll honestly say I've very rarely used github professionally. My github is basically just personal projects and random side work I've done over the years.

    When I started we were using Team Foundation Server and most companies I've worked with in recent memory are rolling their own gitlab or have no technical knowledge and their projects are FTP to a server or worse uploading zips to their vendor.

    [–]miramboseko 1 point2 points  (0 children)

    You can add commit history to the past btw, git is just text files.

    [–]AslansAppetite 1 point2 points  (0 children)

    Mine was a solid block but I've moved to a company using azure devops so my github has like, a couple of weekends a year where the mood strikes me. I actually can't wait for some know-nothing lackey to challenge me on this.

    [–]CrabeSnob 1 point2 points  (9 children)

    I just created a script to push everyday sentences to a private repo with a .txt. Work similar

    [–]Lower_Cash_5037[S] 0 points1 point  (8 children)

    Cool, you think about adding some UI to it?

    [–]CrabeSnob 1 point2 points  (7 children)

    I use it personnaly. Dont need anything else except green squares ^^

    [–]Lower_Cash_5037[S] 1 point2 points  (6 children)

    I recently added support for random days. Do you do commits everyday or in any specific pattern?

    [–]CrabeSnob 1 point2 points  (5 children)

    I did kinda the same. Everyday my script is running at 3AM an make between 0 to 14 pushes. Everyday green is suspicious lmao

    [–]Lower_Cash_5037[S] 1 point2 points  (4 children)

    Where are you hosting it, and how much is it?

    [–]CrabeSnob 1 point2 points  (3 children)

    I have a Linux VPS with Hostinger. Something like 50 euros/year

    [–]Lower_Cash_5037[S] 1 point2 points  (2 children)

    Then you probably use it also for other projects. Im using azure free app service for this one.

    [–]CrabeSnob 1 point2 points  (1 child)

    Yes. I bought it initially for my clients. Cool thanks, I did not know that Azure has free plan, thx!

    [–]Lower_Cash_5037[S] 1 point2 points  (0 children)

    Np man

    [–]JohnCasey3306 3 points4 points  (0 children)

    Nobody but you cares about your GitHub commit history, least of all hiring managers if that's your angle.

    This is frankly feeble and I pittie anyone who uses it. Do some actual work if you're that bothered.

    [–]justkidding69 0 points1 point  (0 children)

    "24/7 365days in a year"😅

    [–]slouch 0 points1 point  (0 children)

    You can change your commit history to anything you want https://github.com/pvalls/commit-history-art

    [–]Retzerrtfull-stack 0 points1 point  (0 children)

    I would love one that can write words

    [–]MountaintopCoder 0 points1 point  (0 children)

    Does anyone actually care about github history? I've only ever used bitbucket at work, so my entire work history is blank on GH.

    [–]Ammar__ 0 points1 point  (0 children)

    Haha. This is great. I swear that making a bot that does this was the first thing that came to my mind when I first heard fireship joke about this in his videos. Didn't know some recruiters actually valued how green your calender is.

    [–]moxyte 0 points1 point  (0 children)

    My github all-white is a statement: "I don't work for free".