Sunday, May 31, 2026

The honeymoon's over. Big companies are hitting AI cost overruns and actively cutting usage—the opposite of the "use everything" mentality from last year. WSJ reports on enterprises implementing caps, throttling features, and renegotiating vendor contracts. This is the real story behind the spending announcements: the ROI math is harder than advertised. If you're pitching AI tools to enterprises, this is the environment you're selling into.

Microsoft's move from seat-based to token-based billing for Copilot is hitting developers hard—and they're vocal about it. The fear: transparent usage metrics mean sticker shock and team friction over who "costs the most." This echoes Amazon's earlier decision to kill internal leaderboards that made employees chase AI usage metrics. Message to builders: expect your customers to care deeply about consumption costs going forward.

Internal Microsoft research shows that using AI to automate certain tasks costs more than just hiring someone to do the work. When you factor in infrastructure, inference, retraining, and maintenance, the math breaks down for many use cases. This doesn't mean AI is pointless—it means builders need to be ruthless about where it actually saves money. If you're evaluating an AI solution for a company, do the baseline calculation: would hiring a contractor be cheaper?

We covered this yesterday, but the conversation has deepened: MCP (Model Context Protocol, a standard for connecting AI models to data sources) isn't dead, but it's hitting real adoption friction. The post flags a core issue—standards are only useful if they solve a problem cheaper and faster than bespoke solutions. For builders, the takeaway: don't assume open standards automatically win. Shipping fast with a tight integration often beats waiting for ecosystem alignment.

Big money is flowing into European AI infrastructure. SoftBank's bet on French data centers (5 gigawatts of capacity) signals confidence in EU-based AI compute but also reflects geopolitical fragmentation—Europe wants AI independence from US cloud giants. For builders: expect more regional AI model providers, regulatory friction around data residency, and multiple inference regions becoming table stakes.

A fun data point: the latest rsync release includes hundreds of commits authored by Claude, an open-source project volunteer. This is real AI-powered open-source work, not hype. It's a good case study in how coding assistants can reduce friction on maintenance-heavy projects. The bar for "shipping production code written by AI" has quietly gotten very low.

Google is being smart about competitive pressure: they've loosened daily usage caps on Gemini to make it more appealing to power users. The move signals Google knows rate-limiting is an easy way to lose users to Claude and GPT-4. Usage caps are a business decision, not a technical limit. Expect to see more of this as frontier models compete on permissiveness.

Google launched Gemini Spark, a separate always-on AI agent that handles everyday tasks—inbox summarization, event planning, that kind of thing. The product works, but the positioning is confusing: why is it separate from Gemini? The real story: Google is experimenting with task-specific AI frontends that stay in the background. If you're thinking about agent products, this is worth trying to understand what sticks.

Meta's betting on wearable AI hardware—a pendant device that presumably captures audio and context to feed an AI assistant. This is the logical next step after Ray-Bans: AI that lives with you, not on your phone. For builders: hardware+AI combos are becoming a serious product category. If you're thinking about embodied AI or context-aware agents, the form factor matters as much as the model.

A thoughtful essay on what happens to expertise when AI can do "good enough" work in any domain. The argument: expertise isn't just knowledge, it's judgment, taste, and risk-bearing. AI is collapsing the value of commodity expertise while making deep expertise more valuable. Worth reading if you're thinking about career strategy or positioning a business in an AI-saturated market.

Jack Maguire writes candidly about the psychological toll of AI disruption on knowledge workers—the grief, the self-doubt, the fear of obsolescence. This isn't doomerism; it's a genuine human experience that's being underacknowledged. If you're building AI tools that displace people, or if you're on the receiving end of that displacement, this essay names something real. Builders who ignore the human side of disruption do so at their peril.

Simon Willison excerpts Anthropic's technical deep-dive on sandboxing Claude across different product contexts. The core insight: containment isn't about the model, it's about the system around it. If you're shipping Claude or any frontier LLM in production, this breakdown of isolation layers and guardrails is required reading. It's rare to see this level of detail made public.