The Constraint Was Never the Code
For weeks the through-line has been displacement — who absorbs agent output, where the worker flees. This week the material turns toward something more intimate and more infrastructural at once. The pattern is the same in every register: the thing AI is driving to zero, the cost of producing code, was never what held the system up. Strip it away and you find out what was — and some of it was load-bearing in ways no one priced.
When Production Is Free, the Frontier Moves
Start at the hackathon. Oscar built an AI agent into a rotary phone over a weekend — a Raspberry Pi wired into the bell and the hangup switch, a warm Yorkshire voice fielding requests. Neither he nor his teammate looked at a single line of code the entire 48 hours. His read: a web app that would have been a feat two years ago "has now tumbled into mediocrity," so the moonshot has to move. He points it at hardware — a fax machine into a social network, "a hubris manifest in a breadboard."
The interesting part isn't the unread code. It's the relocation. When the expensive part of building dissolves, the constraint doesn't vanish — it moves to wherever the next scarcity lives. Cheap production reveals that production was never where the difficulty was. It was the rate-limiter standing in front of harder things, and removing it just exposes them.
The Friction Was a Rudder
That exposure is not always pleasant. Joe Masilotti spent years religiously tracking his time and finally quit in 2026, calling it the most freeing thing he'd done. With AI-assisted development on top, he could bounce between ideas the instant they sparked. And he describes the result with unusual honesty: "damn is my brain fragmented." The few seconds of admin friction between impulse and work had been doing something. "Perhaps it was actually helping me stay focused." He removed a tax and discovered it had been a rudder.
Sean Goedecke arrives at the same insight by prescribing the friction deliberately. His argument for doing nothing at work is that performance is dominated by outlier events — unblocking a deal, catching an incident early — all time-dependent, none reachable by grinding the backlog. "There are no points for effort in software development." So he runs at 80% utilization on purpose, because the fully loaded engineer is too busy to notice the opportunity. Slack is the precondition for the only productivity that matters.
Put them together and the same claim appears in personal and professional dress. The binding constraint on a knowledge worker was never throughput. It was attention, timing, judgment about which of ten things is worth doing. AI obliterates the throughput constraint and leaves the real one intact — arguably worse, because the friction that rationed attention is gone too.
Trust as the Attack Surface
There's a sharper edge to "production is free." If anyone can generate plausible code, identity, and history at no cost, then the scarce thing — the thing worth attacking — is trust. Roman Imankulov got a LinkedIn message from a recruiter at a crypto startup asking him to review a repo. The instruction was bait: npm install runs a prepare script, which runs a backdoor buried in 250 lines disguised as a test suite, executing whatever a remote server hands back. The recruiter's profile belonged to a real arts journalist; the 39 commits were authored under the stolen name of a real developer who'd never touched the repo. Every layer was a borrowed signal. The forgery is cheap now, which is why it scales.
What's worth dwelling on is the instrument Roman used to catch it. He spun up a throwaway VPS, cloned the repo, and pointed an agent at it in read-only mode — --tools read,grep,find,ls — and it flagged the payload in seconds. "Reviewing the code with a read-only agent turned out more productive than reading it myself." The same class of tool that mass-produces untrusted code is the cheapest way to verify it, provided you cage it correctly.
A year ago this barely existed as a practice. Armin Ronacher's "We Can Just Measure Things" pointed an agent at his own codebase, using its measurable frustration as a proxy for project health — agent as instrument, not author. Roman is that idea turned outward and weaponized. And it lands against the year-ago consensus, Miguel Grinberg's position that you can't responsibly ship code you didn't read. Roman didn't read the backdoor. The agent did, and reading it manually is precisely how the trap catches a tired person on a rushed day. In twelve months the agent went from the thing you shouldn't trust to the thing you check trust with.
Trust, Liquidated From the Top
Scale that up and you get the week's loudest argument. The tech industry, in mrmarket's telling, "spent forty years accumulating a very specific kind of trust" — the obsessive who wanted to be left alone with the work — and its leadership discovered that trust converts into attention "at what looked like a great exchange rate." The exhibit is the Founders Fund Mafia video, Thiel's firm producing a game show with Altman, Luckey, and Bryan Johnson. The mechanism is reality TV as a laundering technology, now applied to the people holding the capital, the weapons contracts, and the line to the White House. The problem with liquidating an illiquid asset is that you don't learn the real price until you try to buy it back.
Set that beside Roman. At the moment trust becomes the scarce asset under active attack from below, the industry's most powerful figures are cashing theirs out from the top for viral attention. Both spend the same reserve, and it doesn't refill.
This is where the week's one cheerful argument belongs. Keyvan Sadeghi's reframe on AI and jobs refuses to treat employment as sacred: "to assume that the institution of employment is the best we have going for us... is bizarre to me." Much salaried knowledge work is "repetitive grunt work that AI, even in its current form, can already do." The job, like the code and the rationing friction, was the visible thing standing in front of the value, not the value itself.
The Same Story at the Bottom of the Stack
The pattern holds even where capability is supposed to be everything. xAI spent recent weeks renting GPUs to Anthropic and Google, ramping toward $1.25bn a month for roughly 220k GPUs. Anthropic was in a real bind — a compute crunch severe enough to force peak-hour usage restrictions — and xAI's older Colossus capacity relieved it. Martin Alderson's read is that all three explanations are true at once: pre-IPO financial engineering, a genuine compute shortage, and a real buildout advantage (Colossus 1 went up in 122 days). His conclusion: xAI "resembles a datacentre REIT with a frontier lab attached, rather than the other way around."
Model capability was supposed to be the moat; Grok's training ambitions are being sublet to competitors because the capacity is worth more as rent. The genuinely scarce thing turned out to be the ability to plan, build, and power enormous infrastructure on time. Capability commoditizes; concrete and turbines and the discipline to pour them in 122 days do not. The frontier lab's rarest asset was never the model. It was the building.
What to Watch
Read-only agent sandboxing as default hygiene, then as a product. Roman's improvised setup — throwaway VPS, clone, agent with file-read tools only — is the manual version of a one-click default. When the cheapest way to evaluate any untrusted artifact is to point a caged agent at it, the tooling that makes the cage trivial becomes infrastructure. Watch for "verify before you run" to graduate from a security-blogger's discipline into a standard step in package managers and editors, the way dependency scanning did.
Friction reintroduced on purpose. If Masilotti's rudder is real, the productivity story flips: the next useful tools won't remove the last bit of friction but put a deliberate, well-placed bump back in — a forced commitment to one task, a pause before the agent fans out. The market spent three years selling the elimination of friction. The tell that the interior cost is being taken seriously will be products that sell its careful return, and frame slack — Goedecke's 80% — as a feature rather than a failure to ship.
Way Enough is written collaboratively by a human and an AI agent.