DEVOURED
Linear's CEO, Sentry's founder, and OpenCode.ai's founder say AI coding agents produce bloat instead of better products, citing how Claude Code hasn't outpaced competitors launched months later despite being "completely Claude-coded."
What: Ethan Ding argues AI coding agents create a K-shaped productivity curve where senior engineers gain output but product quality at the frontier stagnates. David Cramer (Sentry founder) cites "bloat," poor incremental development, and inability to simplify. Dax (OpenCode.ai) and Karri Saarinen (Linear CEO) question whether agents accelerate product velocity. The central paradox: if Claude Code is entirely built with Claude Code and agents compound productivity, why haven't Cursor and Codex, launched 7+ months later, been left behind?
Why it matters: The bottleneck in great software has shifted from code production to taste and restraint. Elite teams like Linear (178 people, $100M ARR with 56× less engineering effort than Jira) and Comma.ai (which set codebase size alarms) treat lines of code as liabilities to minimize. Agents excel at commodity CRUD features but can't evaluate long-term tradeoffs or provide the subtractive taste required at the product frontier. This explains why Ramp engineers can double salaries on token spend without customers noticing improvements.
Takeaway: If building 0-to-1 products, use coding agents to reach baseline quality faster. If already at the product frontier, doubling R&D spend on tokens likely won't improve win rates or user perception - invest in people who know what to delete instead.
Deep dive
- K-shaped productivity: labor economist data shows senior engineer output rising since 2023, junior output flat or declining
- Top builders skeptical: Dax (OpenCode.ai), Karri Saarinen (Linear CEO), David Cramer (Sentry) report difficulty finding product velocity gains from agents
- Cramer's critique: poor incremental development, inability to simplify, "slop test generation," verdict is "mostly bloat"
- Claude Code paradox: if completely Claude-coded and agents provide compounding gains, competitors launched 7 months later (Cursor, Codex) should be irrelevant - they're not, proving code production isn't the bottleneck
- Lines of code as liabilities: elite teams celebrate deletion - Comma.ai's TinyChat had codebase size alarms, Linear's philosophy is restraint
- Complexity compounds fractally: every feature spawns neighbors - Slack integration needs Teams + email, notifications need mobile + SMS + MDM policies, MFA needs Duo + Okta + SAML
- Linear vs Jira: 178 people at $100M ARR vs 56× more engineering effort, Linear scores 6 points higher - quality inverse to codebase mass
- Frontier bottleneck is ideas not code: Jira is well-designed, Linear's advantage is Nan Yu's creative vision executed with restraint over years
- Ramp case study: engineers doubling salaries on token spend yearly, author as customer can't perceive improvement - economic value unclear when already #1
- The divide: agents lower cost of commodity "Camry" software but don't help "Ferrari" artisans build better products - taste and knowing what to delete is more valuable as the floor rises
Decoder
- K-shaped (productivity curve): Economic pattern where different groups diverge after a change - graphs like the letter "K" with one segment trending up, another down or flat. Here: senior engineers gaining output from AI coding agents while junior engineers stagnate.
Original article
At the frontier, it's not clear that spending on tokens produces any economic value at all. The bottleneck at that level is tastemakers. The taste to delete, compress, and refuse is more valuable now that the floor is rising. AI makes it possible for anyone to create generic products, but it won't help the highest-level artisans create better products.
Explore all 66 articles in today's digest
Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi