Drew Breunig spent the weekend making a narrower argument than his headline suggests. His post says Fable marks the end of Moore's Law for models, and the claim underneath is specific: for roughly three years, an engineer who spent a week tuning a coding harness, a context strategy, a retrieval setup, was doing work with a very short shelf life, because the next model would land at the same price or cheaper and paper over whatever the harness was compensating for. Skipping that work was correct. Breunig's read is that the cadence which made it correct has broken. What broke is a depreciation schedule: model progress had been writing off builder-side work at a predictable rate, and that rate just changed.
Work done around a model has always had a half-life, and until this month the vendor set it. Every release wrote off some portion of what builders had assembled on top: the prompt scaffolding compensating for a weak instruction-follower, the chunking scheme working around a small context window, the retry logic wrapped around a flaky tool call. A free lunch is a schedule. Somebody else's improvements retire your work for you, on a cadence you can plan around, and the rational response is to build as little as possible and wait. When the schedule slows, and when the inputs to it get more expensive at the same time, the half-life extends, and effort that behaved like an expense starts behaving like an asset. The frame worth carrying out of this week: every piece of engineering done above a platform has a depreciation schedule, and the interesting question about any platform shift is who controls it.
The slowdown reading has real evidence behind it and deserves to be stated properly. The Financial Times reported this week that Anthropic's flagship is losing users to cheaper tools, which is what a market looks like when buyers stop paying a premium for the frontier. The Rundown covered OpenAI disclosing a pause, now finished, on its largest planned training run, held for further safety testing. A frontier that has stopped pulling away, plus customers who have noticed, is a coherent picture of deceleration.
The prices are what break it. Nvidia has notified customers of AI-related increases above fifteen percent, and DDR5 server memory is up roughly five hundred percent year over year. That is the reverse of ordinary commoditization, where the cost of producing a capability falls as it stops being scarce: inputs are getting more expensive even as outputs have become good enough that buyers shop on price. That combination pushes work toward the place where cost is still controllable, which is everything sitting between the model and the job.
Qwen 3.8 27B is the concrete version. Four separate reports landed in a single day on Hacker News and r/LocalLLaMA: a 39,000-line C codebase ported to a single HTML file, an early-2000s ARM point-of-sale firmware preserved and emulated after Opus 4 failed at it, and an XDA writeup of a thirty-minute reverse-engineering job that a frontier model was supposed to own. None of these are capability demonstrations in the benchmark sense. They are long, boring, token-hungry jobs where the binding constraint is what an hour of grinding costs rather than what the model scores. A 27-billion-parameter model running on hardware you already own changes that arithmetic, and everything that makes it survive contact with a real codebase, the scoping, the compaction, the verification pass, is harness.
This is the second time in twenty-odd years the industry has been told its free lunch is over, and the first time, the trade press got it wrong for about two years. Through the Wintel decade the joke was that Andy giveth and Bill taketh away: Intel's clock speeds doubled, Microsoft's software absorbed the gains, and optimizing anything was widely treated as a waste of a good engineer. Then in 2004 Intel canceled Tejas, quietly dropped the 4GHz Pentium, and clock scaling stopped.
In 2004 I read that as a competitive story, because that was how it was covered. Intel had stumbled on its roadmap, AMD had the better architecture for a cycle, the horse race had a new leader. Herb Sutter's "The Free Lunch Is Over" ran in Dr. Dobb's in March 2005 and named what had actually happened, and it still took a couple of years for the implication to become general knowledge: a decade of skills the industry had actively discouraged, profiling, cache locality, concurrency, had just become the job again. Nobody who kept those skills warm got better at them in 2005. The market repriced them.
Three things are different this time, and they set how long the current arrangement holds. The 2004 wall was physics, and physics does not negotiate; this one is economics and vendor choice, both of which can reverse inside a quarter. The multicore transition made the work genuinely harder, which is why absorbing it took a decade, whereas most harness work is bookkeeping any competent team can do and simply could not justify. And the code being written now mostly wraps somebody else's service, so the thing appreciating belongs to you less completely than a hand-tuned inner loop did.
Linus Torvalds credited an AI with most of the grunt work in what his commit message called a debug session from hell. Simon Willison pulled the caveat out of the same message: the thing repeatedly stated things flat out that turned out to be wrong. Both halves are the finding. Mechanical bisection and trace reading are solved well enough to hand over; conclusions arrive with total confidence and no reliability. That gap closes at the verification step, in code somebody writes and maintains, which puts it outside anything a model release fixes on your behalf.
The same shape shows up well away from infrastructure. Casey Newton wrote at Platformer about building an LLM wiki after Andrej Karpathy described the practice, and the working artifact in that story is a folder of source documents and a process for querying it, with the model itself interchangeable. Slack shipped Slack Code, which drops coding agents into shared channels so people who do not write code can watch and steer software as it gets built. That is a bet that the surrounding structure, who sees the run, who can interrupt it, where the context lives, is the durable part of the product.
Ramp's economics lab published a piece last week arguing that cheap models have not slowed spending with American AI companies. That finding comes out of Ramp's corporate-card panel, which skews venture-backed and tech-forward, so it describes the firms on Ramp's card rather than American business generally. The gap between those two populations is the actual story: the companies most capable of running a 27B model on their own hardware are also the ones still writing the largest checks to frontier vendors. Cheap local inference and expensive frontier contracts are not yet competing for the same jobs.
Which leaves the question the next two release cycles answer. If work above the model has become an asset, it has also become the obvious thing for a vendor to ship. Context management, memory, eval tooling, verification: each of those is a product Anthropic and OpenAI can put in the box, and putting it in the box resets everyone's depreciation schedule to the vendor's calendar. Jensen Huang described the trade from the other side at CES: "You sell a chip one time, but when you build software, you maintain it forever." Vendors accept that maintenance burden when the software holds the customer. So the scaffolding is worth building either way. Whether it stays yours is being decided inside two companies, on a schedule nobody outside them can see.