Fetching from the wire…
Top 5 · 2026-05-12 · source-backed
Shopify built an internal coding agent called River. It generates over half the company's code. And it won't talk to you in private.
That last part is the interesting bit. River operates exclusively in public Slack channels, refusing DMs entirely. Every prompt, every response, every mistake is searchable by anyone at the company. Tobias Lütke designed it this way on purpose, turning the tool into an organizational learning system. When a senior engineer figures out how to prompt River for a tricky data migration, that conversation becomes institutional knowledge. When a junior engineer writes a bad prompt and gets garbage back, that's visible too.
The data coming out of Shopify's deployment challenges something I've heard repeated at every AI conference this year: that AI tools are "the great equalizer" for junior developers. Shopify CTO Mikhail Parakhin told the Latent Space podcast that senior engineers with thousands of problem-solving repetitions are significantly better at prompting River than newer employees. AI amplifies experience. It doesn't replace it.
Parakhin also dropped this: Shopify now spends more on AI review than AI generation. They hit 100% workforce AI adoption with an unlimited Opus 4.6 token budget, and the lesson was that raw generation speed wasn't the bottleneck. Critique quality was. He defended Jensen Huang's "measure engineers by token spend" stance as "directionally correct" but stressed that quality controls matter more than volume.
I think about this a lot in my own work. I use Claude Code every day in my personal projects, and the difference between a good session and a wasted hour is almost never the model's capability. It's whether I set up the problem correctly. Experience compounds when you're orchestrating AI, just like it does when you're writing code by hand.
For engineering leaders: the public-by-default pattern is worth stealing. Most organizations treat AI tool usage as individual productivity. Shopify treats it as collective learning. The org design decision matters more than the model choice. If your engineers are all prompting in isolation, you're leaving the best part on the table.
Each link below shares sources, entities, or timing with this story.
In a Latent Space podcast episode, Shopify CTO Mikhail Parakhin disclosed the most detailed enterprise AI adoption numbers I've seen from a public company. The headline stats: 90-100% of Shopify employees use AI tools daily. The company provides an unlimited Claude Opus 4.6 to...
Mikhail Parakhin doesn't do half-measures. In a Latent Space deep-dive interview, Shopify's CTO (ex-Microsoft, ex-Bing) revealed that 100% of Shopify's workforce now uses AI daily, and the company actively discourages anyone from using a model less capable than Opus 4.6. Not r...
One in eight merged PRs at Shopify is now written by an AI agent. Not a demo. Production code, human-reviewed, shipped to customers. Simon Willison highlighted Shopify's internal River agent with numbers that are hard to ignore: 5,938 employees used it in the last 30 days acro...
This one rearranged my week. An essay published August 4 walks through Databricks' independent benchmark of coding harnesses against its own multi-million-line codebase. Pi, a harness with four built-in tools and a system prompt under 1,000 tokens, paired with Opus 4.8 at xhig...
I've been saying for months that the real gains aren't in switching models. They're in how you set up the environment around the model. Now there's quantitative proof. Stanford IRIS Lab published Meta-Harness, a system that autonomously evolves its own coding harness, system p...
Within five days of each other, both Claude Code (v2.1.158, May 31) and Cursor (3.6, May 29) shipped remarkably similar architectures for autonomous agent execution. Both use a classifier subagent that reviews each pending action against conversation context and decides: allow...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.