📊 Full opportunity report: The Coding Singularity Is Real — and Steeper Than Clark Presented on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

New data confirms AI models now code at near-human levels for routine tasks, suggesting the coding singularity is real and happening faster than previously estimated. Deployment across broader software tasks is ongoing but uneven.

Recent data confirms that AI systems are now capable of performing most routine software engineering tasks at near-human levels, with capabilities surpassing prior estimates and accelerating the approach of the coding singularity.

Two key data points from May 2026—SWE-Bench and METR time horizons—show that AI models like Claude Mythos Preview now achieve 93.9% success on routine coding benchmarks, up from 2% in late 2023. The SWE-Bench scores indicate AI handles the majority of standard coding tasks in frontier labs, although more difficult or unfamiliar tasks still pose challenges.

Simultaneously, METR’s updated time horizon forecasts reveal that the speed of AI problem-solving continues to accelerate, with median completion times decreasing from 100 hours to approximately 24 hours by the end of 2026. These improvements suggest the recursive self-improvement loop—central to the concept of the coding singularity—is unfolding faster than previously projected.

Experts note that while the capabilities are real and significant, deployment across the entire software industry remains bifurcated. Routine, well-understood tasks are increasingly automated, but complex, proprietary, or architectural work still requires human oversight. The overall impact on employment, policy, and investment is significant but uneven, depending on the nature of the software tasks involved.

The Coding Singularity Is Real — and Steeper Than Clark Presented
DISPATCH / MAY 2026 CLARK EXTENDED · CODING SINGULARITY · THE OUTSIDE READ
▲ The Outside Read Coding Singularity · May 2026
The Coding Singularity · Read From Outside the Frontier Lab

The coding singularity is real —
and steeper than Clark presented.

Clark’s data is accurate. The trajectory is plausibly steeper. The deployment is bifurcated. The labor consequence is empirical. The substance is recursive self-improvement.

Jack Clark’s Import AI #455 has a section called “The coding singularity – capabilities over time” that does the heavy lifting for his automated AI R&D thesis. This is the read on Clark’s section from outside the frontier lab. The headline finding: the capability data is real and possibly understated, the deployment reality is more bifurcated than “everyone codes through AI” suggests, and the substantive event is not the coding part — it’s the opening of the recursive self-improvement loop the coding capability makes operational.

codeAI R&Drecursion The wedge · The mechanism · The singularity
The structural read
“Coding singularity” is the right name. Coding is the wedge. The thing on the other side of the wedge is automated AI R&D. The substantive event is recursive self-improvement, which the coding capability makes operational.
93.9%
SWE-Bench Verified · Claude Mythos Preview
From ~2% Claude 2 in late 2023 · ~47× in 30 months
16+ hr
METR 50% time horizon · Mythos Preview · May 8 2026
“Measurements above 16 hrs unreliable with current task suite”
4.3mo
Post-2023 doubling time · METR 1.1 methodology
Faster than Clark’s 7-month figure · 20% steeper curve
−20%
Software dev employment · ages 22-25 · Stanford
From late-2022 peak · age-inverted hiring · empirical
SWE-BENCH 2% → 93.9% IN 30 MONTHS · MYTHOS PREVIEW SATURATING THE BENCHMARK METR 30s → 12hr → 16+hr IN 4 YEARS · TASK SUITE BEING OUT-GROWN BY THE MODELS CURVE STEEPENING POST-2023 DOUBLING TIME RECALCULATED TO 4.3 MONTHS · COTRA REVISED UP DEPLOYMENT 74% GLOBAL DEV ADOPTION · CLAUDE CODE $2.5B RUN-RATE · CURSOR $1.2B ARR LABOR MARKET JUNIOR POSTINGS DOWN 40-50% · STANFORD 22-25 EMPLOYMENT −20% THE STRUCTURAL READ CODING IS THE WEDGE · RECURSION IS THE SINGULARITY SWE-BENCH 2% → 93.9% IN 30 MONTHS · MYTHOS PREVIEW SATURATING THE BENCHMARK METR 30s → 12hr → 16+hr IN 4 YEARS · TASK SUITE BEING OUT-GROWN
The capability data · confirmed and updated

Clark’s numbers check out. Post-publication data is sharper.

Both benchmark trajectories Clark cites are publicly verifiable. Both have moved meaningfully in the week since Import AI #455 was published. The trajectory is plausibly steeper than the essay presents.

The two capability charts · post-publication state
SWE-Bench at saturation noise floor; METR running out of measurement headroom.
▲ FIG. 01A · SWE-BENCH VERIFIED
Real GitHub issues · saturating
Late 2023 · Claude 2~2%
Dec 2025 · Opus 4.580.9%
Apr 2026 · GPT-5.3 Codex85.0%
Apr 2026 · Opus 4.787.6%
May 2026 · Mythos Preview93.9%
Update Clark doesn’t include: on SWE-Bench Pro (harder problems), Mythos 77.8%, Opus 4.6 53.4%, GPT-5.4 57.7%. The gap widens substantially as task difficulty rises. Private-codebase subset drops scores another 5-10 points.
▲ FIG. 01B · METR TIME HORIZONS
50% reliability task duration · out-growing the suite
2022 · GPT-3.5~30 sec
2023 · GPT-4~4 min
2024 · o1~40 min
2025 · GPT-5.2 (High)~6 hr
Feb 2026 · Opus 4.6 (corrected)~12 hr
May 8 2026 · Mythos Preview≥16 hr
End 2026 · Cotra revised median~24 hr
METR 1.1 update: post-2023 doubling time recalculated to 130.8 days (4.3 months) — 20% faster than Clark’s 7-month figure. “Measurements above 16 hours are unreliable with current task suite.” The measurement instrument is the rate-limiter.
The curve is steeper than Clark presented. And the measurement is the rate-limiter.
The deployment reality · outside the frontier lab
AI VoiceWriter – Smart Dictation & AI Writing Assistant for Windows & Mac | USB Dongle & Mobile App for Voice Input, Proofreading, Rewriting & Multilingual Support

AI VoiceWriter – Smart Dictation & AI Writing Assistant for Windows & Mac | USB Dongle & Mobile App for Voice Input, Proofreading, Rewriting & Multilingual Support

🎙️ Hands-Free Voice Typing for Windows & Mac – Powered by iOS & Android dictation technology, AI VoiceWriter…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Five-tool consolidated stack. Bifurcated by segment.

Clark: “frontier-lab researchers code entirely through AI systems.” Correct for frontier labs. Partially correct across the broader market — with substantial segment-level variance. The Cambrian explosion of 2024 has consolidated to five production-grade tools.

The five-tool consolidated stack · May 2026
Concentrated oligopoly with strong brand moats, high switching costs, and platform-grade revenue.
Claude CodeAnthropic · terminal-native
MCP-deep terminal agent. Strongest on hard tasks. The senior-engineer surface. CSAT 91%, NPS 54.
$2.5Brun-rate
18% global
24% US/CA
CursorAnysphere · IDE-native
VS Code fork with Composer 2. The default IDE agent. Credit-based billing the persistent complaint.
$1.2BARR
18% global
50%+ F500
GitHub CopilotMicrosoft · multi-model since Feb
Widest reach, slowest growth. Enterprise default. Now backs Claude + Codex in addition to GPT.
$$$est large
29% global
40% large ent
OpenAI CodexGPT-5.5 · post-Windsurf rebrand
Cloud-task-runner pattern. Async delegation surface. Acquired Windsurf for ~$3B in late 2025.
growing2026
~60% of
Cursor usage
DevinCognition · async autonomous
Most autonomous. Submit task → return PR. Highest demand on review discipline. $20 + $2.25/ACU.
nichegrowing
~5-10%
professional
Adoption by segment · the bifurcation
Frontier labs (Anthropic, OpenAI, DeepMind)
~100%
AI-native startups + Bay Area tech
~90%
Big tech (FAANG-adjacent)
60-75%
Mid-market enterprise
40-55%
Regulated industries (health/finance/gov)
15-35%
Long-tail enterprise + small IT shops
10-25%
The labor market consequence · observable, not theoretical
Design Multi-Agent AI Systems Using MCP and A2A: Engineer your own Python-based agentic AI framework with tool use, memory, and multi-agent workflows

Design Multi-Agent AI Systems Using MCP and A2A: Engineer your own Python-based agentic AI framework with tool use, memory, and multi-agent workflows

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Stanford data confirms what Clark’s data implies.

Junior software engineering postings down 40-50% since 2024. Age-inverted hiring relative to historical software engineering patterns. The data is unambiguous on the entry-level segment. The longer-term consequences are unresolved.

The labor market data · current as of May 2026
Total dev employment up moderately; composition shifted toward mid-career and senior workers.
−40 to −50%
Junior dev postings since 2024
Junior dev job postings on major platforms. Some companies eliminated the role entirely. Bootcamp placement rates have cratered. CS graduates taking significantly longer to find first roles.
Source · multiple platforms · aggregated
−50%
Big Tech fresh-grad hiring 3-year decline
Big Tech hired 50% fewer fresh graduates over 2022-2024 than prior three years. Companies adopting AI cut junior dev hiring 9-10% within six quarters. Pattern is statistically robust.
Source · Harvard research · SignalFire
6.1 / 7.5%
CS / CompEng graduate unemployment
Computer science 6.1% · computer engineering 7.5%. Higher than fine arts (3%), nursing (1.4%), elementary education (1.8%), civil engineering (1%). CS unemployment was below 3% for most of the prior decade.
Source · Federal Reserve · 2025
−6 / +9%
Age-inverted hiring 22-25 vs 35-49
AI-exposure occupations: 22-25 cohort employment −6%, 35-49 cohort +9%. Software engineering historically favored younger workers. Now older workers gaining hiring share. Stanford 22-25 dev employment −20% from late-2022 peak.
Source · Stanford Digital Economy Lab
The structural read · coding is the wedge
FOXWELL NT301 OBD2 Scanner Live Data Professional Mechanic OBDII Diagnostic Code Reader Tool for Check Engine Light

FOXWELL NT301 OBD2 Scanner Live Data Professional Mechanic OBDII Diagnostic Code Reader Tool for Check Engine Light

【Vehicle CEL Doctor】The NT301 obd2 scanner enables you to read DTCs, access to e-missions readiness status, turn off…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

“Coding singularity” is the right name.

Clark calls it “the coding singularity.” The phrase is correct. The framing implies the significance is about coding. The actual significance is what the coding capability enables. Coding is the wedge. The thing on the other side is the singularity.

The recursive loop · what the coding singularity opens
Same capability that produces SWE-Bench saturation is the capability that produces automated AI R&D.
automates produces trains LOOP code SWE-BENCH 93.9% AI R&D METR 16+ HR HORIZON recursion SUCCESSOR TRAINS SUCCESSOR code’ NEXT GEN · BETTER the singularity RECURSIVE SELF-IMPROVEMENT

SWE-Bench saturating means the broader AI engineering capability has reached saturation. AI R&D is engineering with model training as the target output. The coding singularity is what you see. The recursive self-improvement loop is what you are looking at.

What this means · five audiences
Zero to GenAI Product Leader: The complete playbook for AI product management in the GenAI and Agentic AI era

Zero to GenAI Product Leader: The complete playbook for AI product management in the GenAI and Agentic AI era

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Five audiences. Five different obligations.

The coding singularity has specific implications by stakeholder. The institutional response cycle in most democracies is longer than the cadence the data implies.

Stakeholder implications by audience
Calibrated to the empirical data, not to either techno-optimist or doomer framings.
▲ FOR SOFTWARE
ENGINEERS
Bilingual engineer beats monolingual engineer.
“Code quality” is depreciating; “code review quality” is appreciating. Skills that retain value: engineering judgment, architecture, regulatory understanding, agent supervision. AI tool fluency is table stakes, not differentiation. Develop agent orchestration skills now. The bilingual (direct coding + agent orchestration) engineer outperforms either monolingual extreme.
▲ FOR SOFTWARE
BUSINESSES
Engineering capacity stops being the moat.
30-50% productivity gains in serious AI-tool deployments. Competitive advantages that depended on engineering capacity are eroding. What replaces them: distribution, data network effects, domain specialization, regulatory expertise, customer relationships, brand. SaaS moat strategy needs explicit re-examination. The middleware layer (Cursor, Claude Code) is the new moat-rich position.
▲ FOR POLICY
PROFESSIONALS
The empirical question is resolved.
Labor market data resolves whether AI is affecting cognitive-work employment. It is. The policy response — reskilling, transition support, social safety net, education updates — needs to operate on the cadence the data implies. “Missing generation” problem is the near-term concrete consequence. Public sector tech employment may need to maintain pipelines private sector employers are cutting.
▲ FOR
INVESTORS
Productivity story misses the structural story.
(a) Frontier-lab equity captures upside if alignment is solved. (b) AI coding platforms are the immediate value-extraction layer — Cursor $1.2B ARR, Claude Code $2.5B run-rate. Moat real, defensibility against new model entrants the open question. (c) Human-labor-heavy software businesses face structural margin pressure. The thesis reading this as a productivity story underperforms the thesis reading it as structural reorganization.
▲ FOR
EVERYONE ELSE
If you wanted unambiguous evidence, this is it.
Public benchmark data + labor market data + deployment data + tool revenue data is the strongest available evidence that the AI transition is operational rather than speculative. The window for understanding and positioning is the same 32-month window the Clark series synthesis describes. Institutional response cycles in most democracies are longer than 32 months. What gets built during the window determines the equilibrium.

The coding singularity is the canary. The mine is what matters. Software engineers and developer-tool investors are paying attention. Alignment researchers and policymakers are paying less attention than the math suggests they should.

— The structural read · May 2026

Implications of Accelerating AI Coding Capabilities

The confirmed acceleration of AI coding abilities signifies a pivotal shift in software development, with automation reaching levels that could reshape labor markets, software innovation, and policy frameworks. The rapid pace suggests the approach of the coding singularity—an inflection point where self-improving AI systems begin to drive their own evolution more autonomously, with profound technological and economic consequences.

For software engineers and businesses, this means a shift toward more AI-assisted development, potentially reducing demand for routine coding labor but increasing the importance of oversight, architecture, and strategic design. Policymakers and investors must prepare for a landscape where AI-driven automation could disrupt existing industries and create new opportunities.

Recent Advances in AI Coding Benchmarks and Forecasts

Since late 2023, AI models like Claude Mythos Preview and GPT-5 have shown dramatic improvements in coding benchmarks, with Mythos achieving near 94% success on SWE-Bench verified tasks. These benchmarks measure AI performance on routine coding tasks, primarily in familiar codebases, and are considered indicative of the AI’s ability to handle a significant portion of software engineering work.

Simultaneously, updates to the METR time horizon metric—used to forecast problem-solving speed—have shown a faster doubling time since 2023, with median task completion times dropping sharply. These developments support the thesis that AI systems are rapidly approaching a point of recursive self-improvement, central to the concept of the coding singularity.

While these data points confirm the trend, experts caution that the broader deployment landscape remains bifurcated, with more complex and proprietary tasks still resistant to automation. The full impact on the software industry will depend on how quickly these capabilities translate into widespread, practical application.

“The data confirms that AI models now code at near-human levels for routine tasks, and the pace of improvement suggests we are closer to the coding singularity than previously thought.”

— Thorsten Meyer

Uncertainties About Full Industry-Wide Deployment

It remains unclear how quickly and extensively AI capabilities will be adopted across the entire software industry, especially for complex, proprietary, or high-stakes projects. The current data reflects performance on benchmark tasks, which may not fully represent real-world challenges.

Moreover, the timeline for reaching widespread autonomous self-improvement remains uncertain, with potential technical, regulatory, and economic barriers still to be addressed.

Next Steps in Monitoring AI Coding Progress and Deployment

Researchers and industry leaders will continue to update benchmarks and forecasts, with particular focus on how AI handles complex and unfamiliar codebases. Monitoring deployment trends across different sectors will clarify how quickly the coding singularity influences the broader software market.

Investors and policymakers should prepare for rapid changes, with ongoing assessment of AI’s impact on employment, innovation, and regulation expected over the coming months and years.

Key Questions

What is the coding singularity?

The coding singularity refers to the point where AI systems reach a level of capability that allows them to improve and evolve their own coding abilities autonomously, leading to rapid, recursive self-improvement.

How reliable are current AI coding benchmarks?

Benchmarks like SWE-Bench provide a strong indication of AI’s capabilities on routine tasks, but they do not fully capture performance on complex, proprietary, or unfamiliar codebases. They are useful but limited measures of real-world deployment potential.

When might AI fully automate all software engineering tasks?

While progress is rapid, full automation of all software engineering tasks depends on overcoming technical, economic, and regulatory challenges. Experts suggest that routine tasks are increasingly automated, but complex architectural work may take several more years.

What are the possible impacts on software jobs?

Automation of routine coding could reduce demand for certain roles but increase the importance of strategic, architectural, and oversight skills. Overall, the industry may see a shift rather than a disappearance of software jobs.

What should policymakers do to prepare?

Policymakers should monitor AI deployment trends, consider regulations for autonomous systems, and support workforce transition initiatives to adapt to the evolving software landscape.

Source: ThorstenMeyerAI.com

You May Also Like

NVivo for Qualitative Data: Text and Sentiment Analysis

Unlock the potential of NVivo for qualitative data analysis and discover how text and sentiment insights can transform your research—continue reading to learn more.

Why SSD Storage Matters More Than You Think for Data Analysis

Harnessing the power of SSD storage can revolutionize your data analysis; discover how it transforms your workflow and boosts efficiency like never before.

Laser vs Inkjet for Graduate School: The Smarter Pick

Discover why a laser printer might be the ideal choice for graduate students, but what other factors could influence your decision? Keep reading to find out!

Disk Is the Contract: Inside Threlmark’s Local-First Architecture

Discover how Threlmark’s local-first design treats disk storage as the core contract, enabling portability, resilience, and seamless AI integration in project management.