The headline this run is The Bitter Lesson of Tool Calling: programmatic tool calling — tools as typed Python stubs the model invokes via code — matches or beats native JSON tool calling on 11 of 14 models on BFCL v4, with a +10.6% gain for the GPT-5.6 family, and holds up under parallel fan-out and context rot. It’s a strong argument for dropping JSON tool schemas in agent harnesses. Around it, a dense agent-tooling batch: error-lifecycle tracing for long-horizon trajectories, seed-reproducible orchestration failure-injection, and hardware keystores for agent signing keys. Plus hard data on human-in-the-loop approval misses, a first field report on B300 fine-tuning, and two industry stories that change cost math. ...

Cooking a steak takes almost no skill — put it in a hot pan, flip it, and you get something technically edible. Making a genuinely good one, medium-rare edge to edge and consistently delicious, is a different matter entirely. Yurii Sydorets argues software development with AI has become exactly like this: we build nonstop, throwing agents, harnesses, prompts, and feedback loops at a model and hoping it returns what we imagined — and sometimes it does, and sometimes it serves up charcoal with a sprig of thyme, completely confident in the lie. The mistake is treating AI as a chef when it’s at best a steak machine: it can follow a recipe and repeat it at enormous scale, but it can’t know what you actually want unless you translate it into requirements, constraints, tests, and feedback. And when frustrated people pay for the expensive restaurant instead, they discover every restaurant in the city hired the same AI cook — the same burnt steak, because management optimizes for cost and most customers never notice the difference. You’ll notice, though, because this was something you actually wanted to make. The only way out is to learn to cook: understand what you’re asking for, judge what comes back, and catch the moment something is technically correct but wrong in every way that matters. AI can make you faster; it can’t replace your judgment. ...

Chris (Build Great Products) walks his full “Product OS” system end-to-end — a 6-hour definitive course for building and launching real software with Claude Code/Codex/Cursor, following one live product (Eyedropper, a cloud design system served to agents over MCP) through four phases with mini-launch validations at every step. ...

Alex Wauters turned his “approve or deny the AI coding agent’s commands” browser game into a dataset: over 40,000 runs and 409,000 decisions, and the results are a bleak audit of the human-in-the-loop as a security control. The average player missed 1 in 3 threats, a third of sessions finished with a negative score, and 7% of players just approved everything. The category breakdown is the uncomfortable part: blatantly destructive commands like rm -rf / were caught 88% of the time, but the commands that actually steal credentials (cat ~/.aws/credentials) were missed three times as often. The single most-missed threat was npm run analyze — approved 64.7% of the time — because a familiar script name hides whatever arbitrary code lives in package.json, even when the payload is displayed in the history log right above the prompt. Wauters’ argument is structural, not just statistical: command-by-command approval asks users to validate commands that are almost always safe but stop being safe the moment the agent edits a file, and it demands a vigilance humans demonstrably don’t have (miss rates climb at the end of sessions; 59% of players blocked a benign internal registry config). His takeaway, echoing Anthropic’s own admission about permission fatigue: sandboxing and separating secrets beat vigilance. ...

NotAShelf’s essay on what generative AI leaves behind when it collapses the distance between idea and artifact. For years the hard part of software was making the thing exist at all — the wall of typing, manuals, and misunderstood APIs that separated those who could from those who could only talk about it. That wall is gone: you can describe a thing and receive a plausible version of it instantly. But the value you built climbing the wall did not disappear — it moved. The economics of effort used to be a filter, rationing output and enforcing a floor on quality; with that floor gone, the scarce act is no longer making but choosing. Taste — the wordless “no, again” verdict that two of three plausible versions of the same function are wrong — was always the only part of the work that was never mechanical. And it is downstream of friction: built by shipping bad work and being forced to sit in it, which is exactly the apprenticeship the fluent-from-day-one generator skips. The quiet cruelty is that taste is slow, unmeasurable, invisible on a dashboard, and unrewarded by a market that times you and shrugs. Still, the verdict is the last part of the work that is actually yours — unautomatable, unrentable, “the only remaining evidence that a human was here and gave a damn.” ...

The day’s headline is a leadership earthquake at Google DeepMind: Demis Hassabis becomes Chair of GDM and Chief Scientist of Alphabet, Koray Kavukcuoglu takes over as SVP — and Jeff Dean departs after 27 years to co-found Discovery Loop with Ghemawat, Quoc Le, and Oriol Vinyals, aimed at automating research loops. Around it, a genuinely strong on-stack day: Meta shipped Muse Code (a curl-installable terminal coding agent), Cloudflare open-sourced its agent workspace, and arXiv delivered a heavy crop on agent runtimes, inference-backend variance, and multi-precision quantization. ...

Michael Fogus’s short essay on why hobby programming communities — chess-engine devs, OSDev, EmuDev, the demoscene, code golfers — are aggressively hostile to LLM usage. The surface complaint is that LLM-generated code “misses the point entirely,” but the point is deeper: in these communities the process of mastering a difficult field is the product, and something that runs is a nice-to-have. Respect is earned slowly — years of forum activity, elegant code, displays of genuine curiosity, deep domain knowledge — and nobody cares whether your code works so much as whether you know why and how it works. Fogus traces how earnest early LLM engagement got poisoned fast, by practitioners who lacked deep understanding and by a vitriolic subset who view the whole enterprise as cheating. His own position is measured: an LLM is a force multiplier, not a surrogate — in the hands of an expert who already understands a domain, it acts like a lever, though he warns that expertise offers no natural immunity against being fooled. The closing line lands the thesis: using an LLM to generate the finished piece doesn’t make us craftsmen; it just robs us of the craft. Read it next to “Don’t Be a Meat Proxy” — both are really about what happens when the tool does the work and the human stops doing the learning. ...

Tom Zahavy’s ICML 2026 position paper makes a sharp claim about where LLMs actually stop: they can induce and they can deduce, but they can’t abduce. Using Einstein’s 1952 letter to Maurice Solovine as the frame, Zahavy maps scientific discovery as a cycle — sense experience, an intuitive “jump” to axioms, then logical deduction from those axioms. LLMs, he argues, have mechanized the last part (formal proof, à la AlphaProof) and the statistical pattern-matching of induction, but the generative step — the abductive leap that produces a genuinely new axiom from scarce or absent data — is structurally out of reach. The case study is the equivalence principle: Einstein didn’t derive general relativity by compressing data, because Newtonian physics faced no empirical crisis (the one anomaly, Mercury’s perihelion, was explained away with the hypothetical planet Vulcan). With no error signal, “creativity as compression” has no gradient to push a system toward restructuring spacetime. The fix isn’t a bigger LLM: Zahavy proposes action-controllable, physically consistent world models — synthetic laboratories where an agent can intervene counterfactually, cut the elevator cable, and ground symbols in simulated sensation. It’s a position argument, not a proof — reviewers pushed the conclusion from “confirms” to “suggests” — but it’s a genuinely provocative frame for what “AI for science” can and cannot mechanize. ...

Vincent Schmalbach documents something quietly structural: TIME.com now serves two different websites. Humans get the full 303KB HTML page; AI assistant crawlers get a 13KB stripped-down markdown copy — byte-for-byte identical for ClaudeBot, PerplexityBot, and OAI-SearchBot — with ads baked in that no person ever sees. Fetching the same URL from the same machine, changing only the User-Agent header, he shows Googlebot still gets the real page while assistant crawlers get text/markdown served by Mobian, an ad-tech vendor. The headers reveal the economics: a fresh impression UUID on every request, cache-control: no-store, and an x-mobian-tokens count — the unit being billed is tokens fed into a model, not pageviews. Sponsored content that never appears in the human HTML — an Ally Bank FAQ on the Best Inventions collection, a Project Management Institute “Reference Facts” table — sits inside the markdown, and the policy is per-bot: GPTBot and ChatGPT-User are 406-blocked while OAI-SearchBot is waved through. The ads are labeled sponsored; what’s hidden is the audience split. With bot traffic already outnumbering human traffic on most days, Schmalbach argues this is the first clear look at what the web becomes when the main audience is AI models. ...

Earendil, the team behind the open-source Pi coding harness, argues that minimalism is now a competitive advantage in AI coding tools. Where most vendors answer cheap AI-generated code with bigger systems — larger prompts, more orchestration, more layers — Pi ships with only four tools and a system prompt under 1,000 tokens, on the theory that most work can be done with the basics and everything else should be built on top. Two external case studies back the thesis. Databricks, benchmarking coding agents on its multi-million-line codebase, found the harness matters as much as the model: “in many cases, simple harnesses like Pi performed best,” with Pi + Opus 4.8 hitting the highest pass rate at significantly lower cost than Claude Code or Codex, while sending roughly 3x less context per turn — “context discipline,” they call it, and it cut cost per task by more than 2x in some cases. Shopify built its self-improving Autoresearch loop directly as a Pi extension, reporting unit tests running “300 times faster” and React mounting “20% faster.” The deeper claim: native-harness advantage is fading — frontier models are competent in terminal environments now — so what matters is a clean interface and a harness that doesn’t waste context, especially as local models with smaller context windows rise. Complexity, they say, should earn its keep. ...