Felix Rieseberg Says AI Shifts Software Pareto Principle to 98/2 Ratio

Claude

Apr 28, 2026

Anthropic engineer Felix Rieseberg argues that agentic coding has broken traditional software time estimates by making the initial 80 percent of work nearly instantaneous. This shift moves the engineering bottleneck entirely to the final 2-5 percent of a project where human oversight is required to sweat the details.

Felix Rieseberg, engineering lead for Claude Cowork at Anthropic, observed that AI has fundamentally altered the Pareto Principle for software development. He suggests the ratio has shifted toward 98/2 because getting a feature to a "basically works" state is now nearly instant, while final details still require significant time.

This recalibration reflects the impact of Claude Cowork and its autonomous mode on the software lifecycle. While traditional development followed a predictable curve, AI-native engineering front-loads code generation. This mirrors Andrew Ng's analysis that the primary bottleneck has moved from writing code to strategic verification.

You should adjust roadmaps to account for this "illusion of completion" where a functional prototype no longer signals a task is nearing the finish line. As Claude Desktop integrations accelerate the initial build, focus must shift toward the final sliver of work — debugging and polish — that still requires human time.

View the full update on x.com

Felix Rieseberg

@felixriesebergApr 28

AI has broken my mental model for time estimates. I used to lean on Pareto's 80/20: first 80% of the work takes 20% of the time. I think the underlying principle is still true, but both ratio and curve have moved. Getting to "basically works" is nearly instant, sweating every single last detail still takes a decent chunk of time. Maybe it's time to switch to 90/10, 95/5, 98/2?

4118

View on X

Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →

See all AI news & updates from Anthropic →

Keep reading

Andrew Ng Outlines Organizational Shifts for AI Native Engineering Teams

Andrew Ng argues that agentic coding has shifted the primary software development bottleneck from writing code to strategic decision-making. This transition forces engineering teams to adopt lower product manager ratios and requires developers to expand into design and marketing roles.

Simon Willison Reports Professional Engineers Are Succumbing to Vibe Coding

Simon WillisonMay 7

Simon Willison Reports Professional Engineers Are Succumbing to Vibe Coding

Simon Willison observed that the distinction between casual vibe coding and professional agentic engineering is disappearing as AI agents become consistently reliable. He warns that even veteran developers are treating agents as black boxes, shifting the primary software bottleneck from writing code to design and verification.

Andrej Karpathy Outlines the Shift From Vibe Coding to Agentic Engineering

Andrej KarpathyMay 7

Andrej Karpathy Outlines the Shift From Vibe Coding to Agentic Engineering

Andrej Karpathy detailed a transition toward an agent-native economy where LLMs serve as the primary substrate for computing rather than just tools for acceleration. He introduced agentic engineering as a high-ceiling discipline for building reliable autonomous systems that replace classical code with natural language instructions.

Salesforce scales agentic engineering with Claude Code to accelerate migrations 18x

ClaudeMay 29

Salesforce scales agentic engineering with Claude Code to accelerate migrations 18x

Salesforce has transitioned its global engineering team to an agentic workflow by standardizing on Anthropic's terminal-based agent. The shift resulted in a 151% increase in effective code output and a 5% reduction in incidents. This demonstrates that autonomous agents can improve software quality while significantly increasing development velocity at enterprise scale.