Fixing the AI slop problem in open source
Bill Doerrfeld | March 29, 2026
My
latest feature for The New Stack looks into solutions being proposed to fix open source Slopmageddon.
Open source maintainers are getting hammered by AI slop contributions. These take 12x more time to review, says one developer.
It's a messy evolving issue right now. The kind of topic I like exploring with deep feature articles. ๐
Over the past month I've been talking to a number of folks and looking into stories and research around the topic. Today I'm excited to share my feature for The New Stack.
The verdict? It's gonna take a combination of new platform tools, updated contributor guidelines, vouch and reputation systems, foundation guidance, and community support to fix the problem at scale.
Without trust, open source breaks down. Check it out for an overview of the dilemma and what experts suggest going forward.
Other Blog Posts
Does your agent really need access to every tool call under the sun?
I'll be writing a weekly series for The New Stack this fall covering Kubernetes, cloud native, and everything happening on the road to KubeCon in November.
I'm teaming up with Dan Barahona and AI Security University to put together the MCP Security Conference, a free half-day virtual event dedicated to MCP security .
My latest DirectorPlus edition interviews Shopify's head of engineering, Farhan Thawar, on their unique internal engineering culture.
Neoclouds promise cheaper GPUs and AI-optimized infrastructure, but can they really challenge hyperscalers? My feature on InfoWorld explores their advantages, risks, and likely role in AI compute.
My latest for LeadDev interviews IBM's Neel Sundaresan on how to prevent a decades-old issue in software engineering.
The latest advancement in identity and access management (IAM) is something called zero standing privilege. It's a response to new agentic AI risks.
Big surprise: it's way easier to generate new code with AI than to reuse old code. But what are the long-term effects?
Agentic coding tools have become the default. "When we've taken that away accidentally from people, they scream."
My latest for LeadDev considers how engineering leaders should respond in the wake of uncertainty in the AI model market.
