OMG this took me way too long to get. They replace the substring "ass" ππ
this post was submitted on 05 Nov 2024
867 points (98.9% liked)
Programmer Humor
19483 readers
521 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
and "arse", as seen in charset
Thank you so much I so desperately needed that chuckle right now
I have a friend that works at Salesforce, he told me that they made him change the name of some classes that used the term Blacklist because of inclusivity
This kind of thing is infuriating. Especially when the actual etymology of "blacklist" is a 17th century play where a list of nobles scheming against the British monarchy is described as a blacklist.
But the word black is used so clearly it's racist, right? How can we be woke if we don't randomly ban words because of their alternate meanings?
My previous workplace did the same thing around 2020 with the words whitelist and blacklist and some other words.
It was around the same time when there was news about GitHub moving from master to main/mainline as the default Git branch.
Tangentially related rant: We had a new contributor open up a pull request today and I gave their changes an initial look to make sure no malicious code is included.
I couldn't see anything wrong with it. The PR was certainly a bit short, but the task they tackled was pretty much a matter of either it works or it doesn't. And I figured, if they open a PR, they'll have a working solution.
...well, I tell the CI/CD runner to get going and it immediately runs into a compile error. Not an exotic compile error, the person who submitted the PR had never even tried to compile it.
Then it dawned on me. They had included a link to a GitHub Copilot workspace, supposedly just for context.
In reality, they had asked the dumbass LLM to do the change described in the ticket and figured, it would produce a working PR right off the bat. No need to even check it, just let the maintainer do the validation.
In an attempt to give them constructive feedback, I tried to figure out, if this GitHub Copilot workspace thingamabob had a Compile-button that they just forgot to click, so I actually watched Microsoft's ad video for it.
And sure enough, I saw right then and there, who really was at fault for this abomination of a PR.
The ad showed exactly that. Just chat a bit with the LLM and then directly create a PR. Which, yes, there is a theoretical chance of this possibly making sense, like when rewording the documentation. But for any actual code changes? Fuck no.
So, most sincerely: Fuck you, Microsoft.
Commit with Co-authored-by: Copilot
or maybe better --author=Copilot
It would certainly help evaluate submissions to have that context
dude. i feel that pain.
i got a dev fired because they absolutely refused to test their changes before submitting.
I'm not talking once or twice either. at least a year of that bullshit. i had to show my boss how many hours of wasted time it was taking me because I look at the code first, like literally anybody. Eventually boss pipd them and fired them but holy fuck i wanted to kick that douche in the groin every time i saw a pr with their name on it.
next place I work I'm insisting on a build step success to assign a pr.
Lmao, what, that's wild. How did they justify this??
"it works on my machine."
It's funny that that's the answer that they always gave, considering there were times that we had screen shares, and I asked them to walk me through how they actually got it to work.
When they attempted to try to run it, unsurprisingly it broke.
There were even a few times that I didn't even review it and the first step I took was to inform them that it wouldn't run. Also, unsurprisingly, I was right.
Management at the time was driven by product development and delivery of "high-value" features. As long as deliverables were delivered, this dev could do anything they wanted to. At the end of a year, I'd lost about four weeks of productivity. That doesn't even cover the hours of after work time that I spent on trying to fix their fuckups.
Needless to say, I stopped doing that. I used to be a nice guy to work with, but now... Let's just say if you can't do the work, I'm not covering for you. If your PR doesn't get merged because it's broken and you can't fix it and you spend six weeks trying to fix it, that's on you.
Oof.
My employer pays a buttload of money to CircleCI - for extensive checks (build, lint, formatting, full test suite, as well as custom scripts for translation converage, docs,... for the full tech stack) on every push. Reviews start only when everything passes.
I think you have given me a new-found appreciation for the reasoning behind that decision... π
Surely you have to blame the idiot human here who actually has the ability to reason (in theory)
You think the decision to build this bot like that was not made by a human? Its idiot humans all the way down.
load more comments
(5 replies)
Well, for reasons, I happen to know that this person is a student, who has effectively no experience dealing with real-world codebases.
It's possible that the LLM produced good results for the small codebases and well-known exercises that they had to deal with so far.
I'm also guessing, they're learning what a PR is for the first time just now. And then being taught by Microsoft that you can just fire off PRs without a care in the world, like, yeah, how should they know any better?
load more comments
(1 replies)
I am in doubt. That wouldn't even compile. But who am I to think somebody changing something like this would actually do a test compilation afterwards....
HTML isn't compiled, and unknown attributes are allowed. The best practice is to prefix non-standard attributes with data- (e.g. <div data-foo="test">) but nothing enforces that. Custom attributes can be retrieved in JavaScript or targeted in CSS rules.
clbottomt when the chtopt shows up [imagine this as that popular GIF meme]
We will never solve the Scunthorpe Problem.
there's a very trivial solution that always works actually, it's called "stop being a prude"
It's a clbuttic
Truly in a clbottom of its own
load more comments
(19 replies)
I had a Pycharm linter with "inconsiderate writing list" flag my use of "bi" as inappropriate, recommending to use "bisexual" instead. In my data job, BI, means business intelligence, it's everywhere.
Gotta love Microsoft Power Bisexual
How is that inconsiderate? That's just informal
(Using "bi" to mean "bisexual", I mean, not "business intelligence" lol)
No, it's right.
Business intelligence is inconsiderate and must be stopped!
load more comments
(1 replies)
load more comments
(1 replies)
load more comments
(3 replies)
Holy shit, 10,000 commits because each change was individual (I'm assuming automated).
Those commit messages though π€£
They automated randomization of the commit messages? Wtf?
Gotta appreciate the level of commitment on this commit...
oh god
yeah, no. haha
load more comments
(3 replies)
Fucking Scunthorpes!
I've been tempted to create a bot that does nothing but search comments in code for misspelled words and create pull requests for them.
If it stays in comments, little chance in breaking a working codebase and I'd have an insane amount of commits and contributions to a wide variety of codebases for my resume.
I'll never be a top tier coder. But I might make management.
In case that wasnβt satire, please donβt π₯² A small typo in a comment is not a big issue, and even if the PR is straightforward, a maintainer still has to take some time reviewing it, which takes time away from fixing actual bugs π’
Simple changes require only simple reviews.
load more comments
(1 replies)
load more comments
(2 replies)
Similar vibe:
Google: kill child process
FBI: ΰ² _ΰ²
Google: kill child process linux console
FBI:οΌοΈΆοΈΏοΈΆ)
The ol' master/ slave configuration again....
those are terms, this is substrings within words
I haven't seen branches or variables being called arse
Then again, I do like to catch exceptions as up so I can throw up
load more comments
(1 replies)
When you give the task to an intern-to-be.
Itβs a clbuttic mistake.
The problem was named after an incident in 1996 in which AOL's profanity filter prevented residents of the town of Scunthorpe, North Lincolnshire, England, from creating accounts with AOL, because the town's name contains the substring "cunt".
haha
view more: next βΊ