wow, @shlee made 12 PRs for Pixelfed yesterday <3
Great!
As an user and instance owner: THANK YOU. Shlee
"We have a process to help us build in quality that is based on feedback and inviting human judgement, but if the system incentives constrain our ability to get the feedback, that also means we are less likely to build in quality."
#softwareengineering #pullrequests #vs #mobprogramming #classic
https://www.infoq.com/articles/co-creation-patterns-software-development/
Wondering right now if coding agents will be the end of code reviews. They're already a bottleneck, and agents could multiply code output per developer significantly.
Feels like a better approach might be to "shift the review left": collaborate with the team on the spec upfront, then only run automated checks on PRs. 🤔
If you're serious about reducing lead time, rethink #PullRequests. They add async delays, inflate WIP & often fail to catch real issues. @javisan81 explains why trust-first teams review differently.
Read now: https://javapro.io/2025/10/29/pull-requests-code-reviews/
@Codeberg my problem ain't #scrapers - otherwise I'd #SelfHost my stuff in my own home LAN - but rather #bots flooding #Issues and #PullRequests with garbage.
The problem I dread is once people start abusing their "#AI"#bullshit and #FloodTheZoneWithShit aka. "#AIslop" for no good reason.
And @Erpel 's original issue is just that: #spam in the #IssueTracker...
#Development #Techniques
Review your own Git pull requests · A simple habit can save many headaches later https://ilo.im/168cm6
_____
#Programming #Coding #CodeReview #VersionControl #Git #GitHub #PullRequests #WebDev #Frontend #Backend
Last week, I wrote about my experience working with the team at Cloud Four, and in particular some of their great practices around PR management. Today, I wanted to talk specifically about a habit my friend Gerardo Rodriguez got me into: reviewing your own pull request. It’s pretty simple. When you create a pull request in GitHub, click on the Files changed tab, and scroll through the diff. Anywhere you’ve done something new that’s not already explained by in-code comments, add a comment in the GUI about what you did and why.
"The basic idea of doc bug zero, as I explained in Defining bug zero, is to clear out all the tickets in the doc issue queue, essentially to finish all your documentation work. Doing so would be the ultimate statement about the productivity gains from AI. Despite my attempts to get to bug zero, it still eludes me. I’m realizing that there’s an art to working through a bug queue, and AI can only take me so far. Good project skills are also needed. One of those skills, which I’ll address in this post, is making it easy for people to review the changelists, or pull requests. (The terminology used in my area of doc work is changelists, or CLs, so that’s how I’ll refer to them here.)"
https://idratherbewriting.com/blog/make-easy-to-review-changelists
#TechnicalWriting #SoftwareDocumentation #ZeroBugs #Changelists #PullRequests
The basic idea of doc bug zero, as I explained in Defining bug zero, is to clear out all the tickets in the doc issue queue, essentially to finish all your documentation work. Doing so would be the ultimate statement about the productivity gains from AI. Despite my attempts to get to bug zero, it still eludes me. I’m realizing that there’s an art to working through a bug queue, and AI can only take me so far. Good project skills are also needed. One of those skills, which I’ll address in this post, is making it easy for people to review the changelists, or pull requests. (The terminology used in my area of doc work is changelists, or CLs, so that’s how I’ll refer to them here.)
#PullRequests increase latency, not quality. Learn why async PRs hurt lead time—and what better code reviews look like.
Javier Lopez Fernandez on collaborative reviews, trust, and flow - read his #JAVAPRO article: https://javapro.io/2025/10/29/pull-requests-code-reviews/
N-gated Hacker News
Jörgi
Jon Fazzaro
Jan David 
JAVAPRO
Kevin Karhan 
Inautilo
Miguel Afonso Caetano