Why Your Best Developers Are Getting Better While Everyone Else Falls Behind

The promise of AI coding tools has been nothing short of astonishing. AI will replace your need to hire software developers and transform your existing developers into 10x engineers. According to this commonly believed view, AI will revolutionize software development productivity across the board, making the entire world better.

But is this truly a potential reality? A new report from GitClear paints a very different picture. After studying over 2,000 developer-weeks of data, the report shows what I and many others have suspected all along: all is not rosy in the AI coding world.

In fact, the report documents an alarming trend. It turns out that AI coding assistants aren't democratizing programming skills after all. They're widening the gap between your highest performers and the rest of your development team.

The "Steroid Effect"

At first glance, the GitClear report seems almost too good to be true. Developers who heavily used tools like Cursor, GitHub Copilot, and Claude Code showed 4-10x higher output across nearly every metric: commits, durable code changes, pull requests, and test coverage.

Truly, the AI-driven 10x future in software development must be at hand.

But as with most things that seem too good to be true, there was more to the story. Much more. In my view, there are three critical confounding factors that can explain much of this dramatic gap:

Senior engineers adopt AI first. The developers showing the highest AI usage aren't representative of your average team member. They're senior and staff engineers who already touch more of the codebase, prototype aggressively, and push code with less third-party review. These are the people who would be high performers with or without AI.

Startup teams move faster and experiment first. Early-stage companies embrace new tools more aggressively than teams at other companies. The "AI effect" we're seeing is really just the well-documented "startup effect" in disguise.

Developers building rapidly use AI more. When developers are prototyping new features and making sweeping upgrades, they're relying on AI more. AI isn't necessarily causing the extra output—it's simply accompanying it.

The 25% Reality Check

The researchers tested this theory by comparing developers' current output to themselves from a year earlier. If AI truly transforms average developers into exceptional ones, we'd expect to see dramatic year-over-year improvement from each developer across the board.

Instead, the average productivity boost was only about 25%. This is a far more modest level than the expected 10x (i.e., 1000%). This is also much closer to other industry estimates, like Sundar Pichai's 10% figure for Google.

Here we can see the uncomfortable truth. AI coding tools are functioning primarily as useful productivity tools for developers who are already high-performant, high-output engineers. They're not transforming the broader developer workforce.

Put more simply, AI tools aren't making software development skills available to the masses. Rather, AI tools are making the top developers better while leaving everyone else behind.

The Hidden Crisis

But there's an even more alarming finding in this research—one that has serious implications for software architecture and long-term system maintainability.

AI power users are generating nearly 10 times more code churn than they did in the previous non-AI world.

Code churn—code that is written, then almost immediately rewritten or deleted—isn't just wasted effort. It's a leading indicator of technical debt accumulation, architectural inconsistency, and long-term maintenance burden.

What This Means for Your Organization

This isn't about whether to adopt AI—that ship has sailed. It's about how to adopt it wisely.

👉 Read the full version of this article, and see the GitClear report online: https://softwarearchitectureinsights.com/articles/ai-productivity-paradox

What's your organization's approach to AI coding tools? Are you seeing similar patterns with your development team? Share your experiences in the comments.