-12
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Jul 2023
-12 points (28.6% liked)
Programming
17314 readers
104 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I would be alarmed if someone on my team or a potential new hire had a completely unbroken GitHub streak, let alone if they felt the need to maintain it via automation.
I actually try to keep my streak going manually, this is just a fallback in case i couldn't commit like on days i go to college or stuff. and i started to learn python that is why i wrote it. i see your point it might be a red flag for some people
You’re also gamifying a system that could be interpreted as an attempt to misrepresent your genuine activity, while also completely missing the point of the activity graph.
In my experience, this would cause a seasoned interviewer to ask more prying questions about your work quality and its volume versus someone who had a less consistent pattern of GH activity.
Volume != Quality
it doesn't create 'Volume'. it does bare minimum, only 1 commit per day even that in case i haven't committed anything on that day.
Is it really that bad? i thought it might be a good idea.
I guess i should just private it and make another copy which people can use that doesn't actually commit to my account.
I think you made something “innocent” in intent without understanding the effect or impact it may have.
I presume you think having a longer commit streak is something that’s valuable, noteworthy, or shows some meaningful characteristic.
While potentially a seemingly harmless ideal, it says a bit about your lack of experience in the workplace and sets up a slippery slope to a toxic paradigm where programmers are expected to maintain commit streaks as part of their evaluation.
This is not a place you want to work and it’s not an expectation you want to hold yourself or others to.
It isn't the case, Having a completely green graph feels more satisfying than having empty dots in between my graph. i guess i will remove it.
Since i wrote it i know commit graph can be tampered with and doesn't reflect anything valuable.
At the end of the day if you want a completely green graph, you clearly have a mechanism to do so.
The point I’m trying to make is, having said graph will likely cause you more harm than you think, especially if you think “green squares” = “more likely to be hired for a desirable job.” It simply opens the avenue to questions regarding your intentions.
What I’d ask you to reflect on is, why does having a solid green graph feel more satisfying? What makes it so?
Umm... I don't know what to say. I guess I will take it down.
Thanks btw.