Where's the shovelware? Why AI coding claims don't add up
TL;DR Highlight
A 25-year veteran developer debunks AI coding tool productivity claims with real data and software release statistics. If AI truly gives 10x productivity, why isn't there a flood of new software?
Who Should Read
Developers using AI coding tools (Cursor, Copilot, Claude Code, etc.) who wonder 'am I really faster?' or engineering managers considering an AI-first transition.
Core Mechanics
- The METR study showed developers felt 20% faster with AI but were actually 19% slower. Developers are unreliable observers of their own productivity.
- The author coin-flipped between AI and manual work for 6 weeks, measuring time — AI was 21% slower by median, and statistical significance would require 4 more months. No dramatic 2x difference exists.
- Cursor claims 'extraordinary productivity,' GitHub Copilot says 'delegate like a boss,' Google claims 25% faster, and 14% of developers report 10x improvement. These claims fuel management FOMO.
- The author's core argument: if AI truly explodes productivity, Steam games, indie apps, and SaaS launches should surge — but actual release statistics show no such shovelware flood.
- These exaggerated claims cause real damage. Companies use 'AI-first' to cut developer hiring, lower salaries, and compress project timelines to 20% of original.
- As of writing (Sept 2025), global software release graphs show no significant increase after AI adoption — the author's empirical evidence.
- The author doesn't reject AI coding's dream itself, but warns that claimed productivity levels aren't supported by data, and management decisions based on them are dangerous.
Evidence
- A developer shared their manager declared 'we are AI-first' and compressed project timelines to 20% of original. SVP and PM AI mania at unprecedented levels — a stark gap between reality and executive expectations.
- Many comments took a middle ground: 'AI is dramatically useful only for specific tasks.' Clearly faster for learning new APIs, scaffolding, mock creation, and codebase exploration, but no difference or net negative for large existing codebase modifications.
- A former CTO countered with 'infinite X improvement for me' — someone who hadn't been coding hands-on could now build large systems again thanks to Claude Code, noting professional developers and non-developers have completely different experiences.
- Some argued the data (through March-April) was too early since agentic coding only became usable around April-May 2025. One developer built a multi-week CLI tool in a day with agents as a specific counterexample.
- Paul Krugman's internet productivity research was cited — the internet also showed no significant productivity statistical change for 25 years after its debut, suggesting AI's economic effects may not appear until the 2030s.
How to Apply
- To measure AI coding tool impact on your team, use the METR study methodology: coin-flip to split AI/non-AI groups and record actual time spent. Use data, not feelings, to avoid self-deception.
- Don't apply AI tools uniformly — focus on tasks with proven effectiveness (scaffolding, mock writing, new API exploration, boilerplate generation) and pair manual work for complex existing code modifications.
- When executives try to compress timelines citing AI productivity, use the METR study results (perceived +20% vs actual -19%) and software release statistics as evidence for realistic timeline negotiation.
- Multiple comments flagged juniors uncritically accepting AI-generated code. During code reviews, especially check AI-generated code for style guide compliance, existing library usage, and PR size.
Terminology
Related Papers
What happened after 2k people tried to hack my AI assistant
실제로 6,000개 이상의 이메일로 AI 에이전트에 prompt injection 공격을 시도한 공개 실험 결과로, Claude Opus 4.6이 비밀 파일 유출을 한 번도 허용하지 않았지만 실험 설계의 현실성에 대한 논란이 뜨거웠다.
When Does Combining Language Models Help? A Co-Failure Ceiling on Routing, Voting, and Mixture-of-Agents Across 67 Frontier Models
여러 LLM을 조합해도 '모든 모델이 동시에 틀리는 비율(β)'이 성능 상한선이며, 업계가 쓰는 pairwise 상관계수(ρ)는 이 상한선을 예측하지 못한다.
Beyond Function Calling: Benchmarking Tool-Using Agents under Tool-Environment Unreliability
실제 환경처럼 API가 망가지거나 결과가 이상할 때 LLM 에이전트가 얼마나 잘 버티는지 측정하는 벤치마크 ToolBench-X 공개.
Nearly Half of LG Smart TV Apps Contain Residential Proxy SDKs
6,038개의 LG·Samsung 스마트 TV 앱을 스캔했더니 2,058개에서 사용자의 IP를 몰래 팔아 트래픽을 중계하는 Residential Proxy SDK가 발견됐다. TV는 컴퓨터처럼 감시받지 않아서 프록시 호스트로 거의 이상적인 환경이다.
Prompt Injection as Role Confusion
LLM이 시스템 프롬프트, 사용자 입력, 툴 출력을 구분하지 못하는 구조적 결함이 prompt injection의 근본 원인이라는 ICML 2026 논문으로, 현재 LLM 보안 아키텍처의 한계를 명확히 분석한다.
GPT-5.5 hallucinates 3x more than MIT-licensed GLM-5.2
모델 크기가 커질수록 성능이 좋아진다는 통념에 반해, 오픈소스 753B 모델 GLM-5.2가 추정 1~2T 규모의 GPT-5.5보다 환각 비율이 3배 낮다는 벤치마크 결과가 나왔다. 단순히 파라미터 수와 벤치마크 점수만으로 모델을 선택하면 실제 업무에서 낭패를 볼 수 있다는 경고다.