In Spotify’s Q4 2025 earnings call on February 10, co-CEO Gustav Söderström made an extraordinary claim: the company’s “best developers have not written a single line of code since December.” The reason? AI—specifically Claude Code and Spotify’s internal system “Honk.” The claim sparked immediate backlash across developer communities, with Hacker News threads generating 200+ critical comments and Reddit’s r/technology seeing 14,000+ upvotes calling it “corporate delusion.” However, developer surveys paint a starkly different picture: 96% distrust AI-generated code quality, and productivity studies show developers are actually 19% slower when using AI tools.
The Semantic Game: What “Not Coding” Actually Means
Spotify’s “best developers” aren’t doing nothing—they’re using natural language to describe changes, which AI implements. Engineers then review, test, and approve the AI-generated code. That’s still coding, just with AI assistance.
Here’s the actual workflow: Engineers use Honk via Slack to request changes. An engineer can describe a bug fix from their phone during their morning commute. Honk generates the code implementation. The engineer reviews the changes on their phone, then merges to production—all before arriving at the office. Spotify’s engineering blog revealed they’ve merged 1,500+ pull requests this way as of November 2025.
Moreover, Söderström’s phrasing suggests developers have been replaced when they’ve actually shifted roles from “writing syntax” to “architecture plus review.” Developers ARE still coding—they’re prompting AI and verifying output. Calling this “not writing code” is technically accurate but deeply misleading, setting unrealistic expectations about AI’s current capabilities.
Why Developers Are Overwhelmingly Skeptical
Developer communities didn’t celebrate Spotify’s announcement—they tore it apart. Three main criticisms dominated the discussion.
First, the supervision problem: If senior engineers spend all their time reviewing AI-generated code instead of writing it themselves, is that actually more productive? Multiple developers on Hacker News noted that reading and verifying code written by something else is often harder and slower than writing it yourself. One engineer put it bluntly: “I can write 100 lines in 30 minutes. Verifying 100 lines of AI code takes me 45 minutes.” The time doesn’t disappear—it just shifts from creation to verification.
Second, selection bias. Söderström specifically mentioned “most senior” engineers made this shift. These are developers with decades of experience who can instantly spot bad code, subtle bugs, and architectural problems. What happens when less experienced engineers try the same approach without that instinct? Furthermore, the claim conflates “senior experts can effectively supervise AI” with “AI can replace coding”—completely different statements.
Third, maintenance and technical debt. AI-generated code that works today still needs maintenance tomorrow. If nobody fully understands the code because a machine wrote it, technical debt could be accumulating invisibly across Spotify’s codebase.
The Data That Contradicts Spotify’s Narrative
Multiple 2026 developer surveys and academic studies directly contradict the productivity claims underlying Spotify’s announcement.
A July 2026 study by the nonprofit research organization METR found that experienced developers believed they were 20% faster when using AI coding tools. Objective tests showed they were actually 19% slower. That’s a striking gap between perception and reality.
Trust in AI-generated code is declining, not rising. Ninety-six percent of developers believe AI-generated code isn’t functionally correct, according to recent surveys. Yet only 48% say they always check code before committing it. Additionally, more developers actively distrust AI tool accuracy (46%) than trust it (33%), and only 3% report they “highly trust” AI output.
The top frustration? The “almost right” problem. Sixty-six percent of developers cite “AI solutions that are almost right, but not quite” as their biggest issue with AI tools. Forty-five percent report that “debugging AI code takes longer than writing it myself.” Consequently, only 16% of developers in Stack Overflow’s survey reported “great” productivity improvements from AI tools.
What Spotify Built (And Why Most Can’t Copy It)
Spotify didn’t just install Claude Code and watch developers stop typing. They built Honk—a custom internal system fine-tuned on their codebase, integrated with their tools, and tailored to their specific workflows.
Honk sits on top of Claude Code as a foundation model, but it includes custom layers fine-tuned on Spotify’s architectural patterns, coding standards, and existing codebase. It’s integrated with Slack for ChatOps, GitHub for pull request management, and Spotify’s deployment pipelines via the Model Context Protocol (MCP). Söderström specifically credited Anthropic’s Claude Opus 4.5 release in December 2025 as the enabler that made this workflow possible.
Most companies lack the resources to replicate this. They don’t have the engineering capacity to build custom AI infrastructure, the senior-heavy teams capable of effective AI supervision, or the robust CI/CD and testing systems needed to catch AI errors at scale. Therefore, Spotify’s success required massive investment in custom tooling, not a plug-and-play solution.
Demand Receipts: What Spotify Didn’t Share
Spotify provided zero metrics to support their bold claim. No code quality data. No bug rate comparisons. No before/after productivity measurements. No information about junior or mid-level developers—only the “best developers” got a mention.
Here’s what we need to see: How much time do engineers spend reviewing AI-generated code compared to the time they previously spent writing it? What’s the bug rate of AI code versus human-written code? Can junior developers use this workflow effectively, or only seniors? What’s the maintainability impact six months later? Is feature velocity actually up, or just developer headcount down?
Without data, this is just a headline. Extraordinary claims require extraordinary evidence, and Spotify hasn’t provided any. Until they do, this looks like PR framing designed to generate buzz during an earnings call, not a technical case study the industry should take seriously.
Key Takeaways
- Spotify’s claim that developers “haven’t written code since December” is semantically true but misleading—engineers are prompting AI and reviewing output, which IS coding with AI assistance
- Developer surveys contradict the productivity narrative: METR study shows 19% slower work pace (not 20% faster), 96% distrust AI code quality, and only 16% see “great” productivity gains
- Spotify built Honk—a custom AI system fine-tuned on their codebase with extensive infrastructure—not achievable with off-the-shelf tools for most companies
- The company provided no metrics backing their claim (no bug rates, quality data, or junior developer outcomes), making this appear more like PR spin than technical reality
- AI coding tools provide genuine value for specific tasks (boilerplate, repetitive code), but the future is “developers working faster with AI assistance,” not “AI replaces developers”
