The Hidden Cost of "Fast" Open Source: Lessons from Wagtail

The core argument here is that the influx of AI-generated contributions is an organizational and cultural challenge, not a technical one. Thibaud Colas and Meagen Voss of the Wagtail CMS team explain that the productivity promised by AI--faster code generation and higher submission volume--creates a significant, hidden tax on maintainers. By treating open source as a social contract rather than a place to dump code, they show that the only way to maintain a healthy project is to intentionally slow down, require human oversight, and prioritize long-term durability over short-term speed. For leaders and developers, the advantage lies in rejecting the pressure to optimize for speed, instead focusing on building sustainable, human-centric systems that survive the hype cycle.

The Illusion of Free Velocity

The most important insight from Colas and Voss is that the cheaper code becomes to produce, the more expensive it becomes to maintain. When AI lowers the barrier to entry, it creates a drive-by culture where the volume of submissions outpaces the human capacity for meaningful review.

> "Code has gotten so much cheaper and implementation is so much easier. So when people come with the pull request does not quite right. And it looks very heavily air generated. We might dismiss the code, but we definitely would want to keep the idea because good ideas, we still definitely value people taking the time to come to our project."
>
> -- Thibaud Colas

This creates a systemic feedback loop: maintainers feel pressure to be welcoming, but the sheer volume of AI-generated content forces them to spend more time triaging than improving the codebase. The competitive advantage belongs to projects that refuse to be pushed by the speed of AI. By enforcing strict disclosure policies, they filter out low-effort noise, allowing them to focus their limited human bandwidth on the high-quality contributions that move the project forward.

The 18-Month Payoff of "Slow" Engineering

Conventional wisdom suggests that adopting the latest AI tools is necessary to stay competitive. The Wagtail team disagrees: they argue that rushing to integrate AI features--like image generation or automated content creation--often introduces energy-intensive technical debt that provides minimal value to the end user.

> "I think that the numbers aren't there to justify that yet. I think it really depends on the individual and their relationship with their work and how much ownership they want to put into that and they wanna stamp their name on it as opposed to like, it just being some generated thing."
>
> -- Meagen Voss

Instead of chasing the latest trend, they focus on moving things left--engaging with contributors during the design and issue-definition phase rather than waiting for a finished pull request. This requires patience that most teams lack, but it creates a lasting advantage. While competitors are busy debugging AI-generated errors, the Wagtail team builds a system that remains stable because the underlying logic was human-vetted and aligned with their long-term architecture.

Routing Around the "Dead Internet"

The system responds to AI-generated content by devaluing it. Voss notes that even search bots and automated systems are beginning to favor human-written content over AI-generated filler. This reveals a critical downstream effect: if you optimize for machine-generated volume, you eventually become invisible to the very systems you are trying to appease.

The Wagtail team’s approach--prioritizing human communication and refusing to automate the voice of the project--is an act of long-term survival. They are betting that in a world flooded with synthetic content, the most valuable asset is a recognizable, human-verified perspective. This is a strategic decision to avoid the atrophy of thought that occurs when developers and writers stop engaging deeply with their own work.

Key Action Items

• Implement an AI Disclosure Policy: Require contributors to disclose AI usage. This creates a filter that discourages low-effort submissions and signals that you value human-authored work. (Immediate)
• Move Collaboration Left: Shift your focus from reviewing finished pull requests to refining issues and design specifications with contributors before code is written. This prevents wasted effort on both sides. (Over the next quarter)
• Benchmark Before Adopting: Before integrating a new AI feature, measure the energy and financial cost against the actual time saved. If the trade-off is negligible, skip it. (Ongoing)
• Prioritize Human-in-the-Loop Communication: Encourage your team to use authentic, even slightly messy, communication instead of AI-polished prose. This builds trust and maintains the human connection that AI cannot replicate. (Immediate)
• Invest in Durable Skills: Shift your learning focus toward AI-free technical fundamentals--like Git, testing, and system architecture--that will retain their value regardless of how the AI landscape shifts. (12-18 months)
• Establish Evals for Your Workflow: Stop guessing if your AI tools are helping. Build simple benchmarks to track whether AI assistance is actually improving your output or just adding coordination tax. (6-12 months)