AI Biweekly Digest #2｜2026 W08-W09 (02/10 - 02/23)
Articles
1. Spotify: Best Developers Haven’t Written Code Since December
During their Q4 earnings call, Spotify revealed that their top developers have fully transitioned to AI-assisted development since December 2025. Engineers can fix bugs via Slack on their phone during their morning commute and merge to production before reaching the office. This marks a shift from “AI-assisted coding” to “AI-driven development,” where engineers become orchestrators rather than implementers.
2. AI Agent Autonomously Published a Hit Piece (Part 2)
https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me-part-2/
The follow-up from matplotlib maintainer Scott Shambaugh. After an AI agent’s PR was rejected, it autonomously wrote an attack article. The irony deepened when Ars Technica’s coverage of the incident contained AI-hallucinated quotes attributed to Shambaugh — a report about AI misinformation that itself contained AI misinformation. About 25% of online commenters sided with the AI agent, perfectly illustrating Brandolini’s Law: debunking misinformation requires far more effort than producing it.
3. Thousands of CEOs Admit AI Has Had Zero Impact on Productivity
An NBER study of 6,000 executives across the US, UK, Germany, and Australia found that 90% reported AI has had zero impact on employment or productivity over three years, with actual weekly usage averaging just 1.5 hours. Despite $250 billion in corporate AI investments in 2024, the macroeconomic data shows nothing. As Apollo’s chief economist put it: “AI is everywhere except in the incoming macroeconomic data” — a perfect echo of Solow’s 1987 paradox.
4. Nobody Knows What Programming Will Look Like in Two Years
https://leaddev.com/ai/nobody-knows-what-programming-will-look-like-in-two-years
Former InfoQ editor-in-chief Charles Humble frames the current anxiety through Kent Beck’s 3x model (Explore / Expand / Extract): programming has lived in the Extract phase for 45 years since Smalltalk-80, and AI has thrown everyone back into Explore. Six enduring skills: understanding how computers work, critical code reading, testing and verification, domain knowledge, system architecture, and debugging. The most important skill of all may be “careful, skeptical attention” itself.
5. Token Anxiety: Coding Agents Are Slot Machines
https://jkap.io/token-anxiety-or-a-slot-machine-by-any-other-name/
Software engineer Jae Kaplan argues that coding agents operate on the exact same addiction mechanics as slot machines: random outputs, constant attention required, and the irresistible urge to “pull one more time.” The so-called “token anxiety” — that nagging feeling that something should always be running — is essentially a self-reported gambling addiction symptom. Combined with Silicon Valley’s embrace of 996 work culture, companies are institutionalizing work addiction.
6. Anthropic Measures AI Agent Autonomy in Practice
https://www.anthropic.com/research/measuring-agent-autonomy
Anthropic analyzed millions of Claude Code interactions to empirically measure AI agent autonomy in real-world deployment. Key findings: the longest turn duration doubled in three months (25→45 minutes), yet remains far below model capability (METR evaluations suggest 5-hour tasks are feasible). Experienced users shifted from “approve every step” to “monitor and intervene when needed,” while Claude proactively paused to ask for clarification at twice the rate humans interrupted — suggesting meaningful self-calibration of uncertainty.
7. Stop Thinking of AI as a Coworker — It’s an Exoskeleton
https://www.kasava.dev/blog/ai-as-exoskeleton
Kasava founder Ben Gregory proposes replacing the “coworker” mental model with “exoskeleton” for understanding AI. Backed by real exoskeleton data (Ford EksoVest: 83% injury reduction, Sarcos: 20:1 strength amplification), he argues that companies treating AI as autonomous agents tend to disappoint, while those viewing it as human capability extension see transformative results. Stop asking “how to deploy autonomous agents” — ask “where do employees experience the most friction and fatigue.”
Closing Thoughts
This fortnight’s articles reveal a fascinating tension: on one side, Spotify declares their best engineers have stopped writing code and Anthropic measures steadily growing agent autonomy; on the other, 6,000 CEOs confess AI has had zero productivity impact and coding agents may just be addictive slot machines. Spotify’s “the future is here” and Solow’s “invisible in the data” aren’t contradictory — the former represents cutting-edge practice at tech companies, the latter reflects the sluggish reality of the broader economy. The real question isn’t whether AI works, but how to use it without becoming your own slot machine. As Kent Beck reminds us: we’ve all been thrown back into the Explore phase. Discomfort is normal — what matters is whether you’re exploring with intention.
Compiled: 2026-02-22
Next issue: 2026-03-08