Mastodawn

👨‍💻 Oh, look! Another gripping tale of an #ARM #developer lamenting the glacial pace of #RISC-V 🐌 while pretending to be productive with Fedora's bug circus. 🎪 But hey, at least he got 86 pull requests in—a testament to truly pioneering 🚀 the art of waiting around! 😂
https://marcin.juszkiewicz.com.pl/2026/03/10/risc-v-is-sloooow/ #Fedora #pullrequests #productivity #HackerNews #ngated

RISC-V is sloooow – Marcin Juszkiewicz

143 vs 36 minutes is far too big difference

N-gated Hacker News Mar 5

Oh look, someone wrote a whole #RFC to politely tell #AI to buzz off with their half-baked pull requests! 🤖🚫 Because, you know, humans have nothing better to do than babysit digital toddlers. Spoiler: If you found this page naturally, congrats, you get to ignore the nonsense! 🎉
https://406.fail/ #PullRequests #DigitalNonsense #TechHumor #HumanVsMachine #HackerNews #ngated

RFC 406i - The Rejection of Artificially Generated Slop (RAGS)

JAVAPRO Mar 4

#PullRequests ≠ Code Reviews. Async PRs often delay delivery, drain trust & boost WIP. @javisan81 makes the case for sync reviews, pairing & post-merge feedback to ship faster with better quality—by building trust into the process.

Read: https://javapro.io/2025/10/29/pull-requests-code-reviews/

#Agile #Java

Show thread

n0mql.com Feb 7

Do I think these changes would make good #PullRequests? Yeah. But I'm disinclined to make PRs, & here's why: I would have to make my case that it's worth changing HIS thing to cater to hams who RX 99.9% of the time, & that's almost assuredly not him. So I don't think he'd ever merge my shit.

Cap Ybarra Feb 3

"Stacked PRs" is a proxy signal for failed engineering culture.

What you are saying is that you either can't/won't make a PR of reviewable size or that your team is incapable of getting reviewable PR's merged in a timely manner, and instead of fixing the problem you have taken the classic software engineering approach of adding an additional layer of complexity so now you have two problems

#programming #pullrequests

Show thread

IBBoard Jan 29

The PR author made changes! So at least it's not a "slop and forget" change.

However, all of their responses have that horrific obsequious tone of LLMs.

And one of my comments was "this call to openFile() seems to render the file, which would be inefficient for multiple files - can you just add it to the database instead?" and their response was "Good point, I've fixed it to be less complicated and more efficient"…

…and then they simplified the OTHER function (which did have more complex async for unexplained reasons)… and it STILL uses the function that I said was inefficient 🙄

Meanwhile, the comments on "this change seems unrelated" got "you're right, that was included by accident, I've reverted it".

I'm calling slop, and I hate the state of the world.

#FuckGenAI #DriveBySlopping #PullRequests #EngageYourBrain

IBBoard Jan 24

I've just read a PR on a FOSS project and… I think it's AI slop 😐

There's nothing much in the code that's blatant slop. It looks reasonable, give or take a weird choice on one function to call. But it's also a function that a human might naively decide to call.

But then there's the PR text. It has footnote-style links. And it says generic and unhelpful things like "swapped X for Y and updated Z"… Yes… I can see that from the diff. But WHY? 🙄

#FuckGenAI #PullRequests #EngageYourBrain

codeDude

Jan 22

Finally #llm policies https://itsfoss.com/news/llvm-ai-policy/ It's gland to read this.

Certainly the #AI is a great tool that could help us in our jobs as #SoftwareEngineers but also I've read bad quality pull request from vibe coders that represent a bottle neck for the code review.

But the human in the loop policies that mentioned in the articles sound like a good start.

#openSource #pullRequests #quality #programming #coding

Open Source Project LLVM Says Yes to AI-Generated Code, But Not Without Conditions

The new "human in the loop" policy holds contributors accountable for reviewing and understanding all AI-assisted submissions.

It's FOSS

N-gated Hacker News Jan 15

🚨 #GitHub threw a tantrum over #Issues and Pull Requests, and now they want us to subscribe for the thrill of OTP déjà vu 🎢🙄. If you ever wanted to be spammed by the world's largest code hoarder, your wish just came true! ✉️🤖
https://www.githubstatus.com/incidents/q987xpbqjbpl #PullRequests #Subscription #Drama #Spam #Alerts #HackerNews #ngated

Incident with Issues and Pull Requests

GitHub's Status Page - Incident with Issues and Pull Requests.

Jörgi Jan 13

wow, @shlee made 12 PRs for Pixelfed yesterday <3

Great!
As an user and instance owner: THANK YOU. Shlee

#pixelfed #pullrequests