Developers have always picked libraries by taste and familiarity. Now an agent makes those calls at machine speed, and most companies have never written down what it should prefer.
TypeSafe's Jev returns a typed agent decision in under 500 milliseconds for a fraction of a cent. Here are ten places in an agent stack where that trade actually wins.
Shopify's return to native Swift and Kotlin looks like an AI story. It's really a lesson in why the efficiency layers in your stack may no longer earn their cost.
Working with AI feels like managing a fast junior developer. But you can only delegate what you can verify, and the agent never grows into someone who can check the work for you.
Google's case for Go is really a case against magic. When a model reads and rewrites your code, legibility stops being a matter of taste and starts showing up in the budget.
A popular claim says exotic languages save tokens when AI writes your code. On real tasks that edge disappears, and the number worth optimizing is the cost of being wrong.
AI slashed the cost of shipping features but not the cost of reliability, so it amplifies whatever your organization already rewards. Most reward the wrong thing.
Stack Overflow's question volume fell 78% in a year. As the public corpus freezes, competitive advantage shifts to the knowledge your company still writes down itself.
Microsoft's engineers merged 24% more pull requests with AI. The constraint didn't vanish; it moved to review, and most teams are still counting the wrong thing.
