posts · 2026-08-30

This one's worth opening because Sander Dieleman is a DeepMind research scientist who works on generative models—his take on diffusion directions carries more weight than a typical survey. The post doesn't push a specific new model. Instead, it walks through the whole arc of continuous diffusion for language from 2021 to now: a burst of embedding-based attempts in 2022, then near-total replacement by discrete diffusion from 2023 onward. The reason for the recent revival is practical—image and audio diffusion have built up a ton of mature sampling and distillation tricks that discrete diffusion couldn't easily use, and continuous methods can just reuse them. If you're tracking whether diffusion models will actually land in language, this is a solid read, but don't expect benchmark tables—it's more of an insider technical retrospective.

This one's worth opening because it fills in yesterday's headline: SpaceX bought Cursor, and OpenAI immediately triggered the termination clause. The statement is blunt—they don't trust Musk's companies to honor service terms, so no more models after Nov 12, including Astra. Musk called Altman a fraud on X. If you code in Cursor, this isn't drama—it's a forced migration. Start pricing the switch to Copilot or Codex. A few other numbers worth scanning: OpenAI's revenue breakdown shows API at only ~$3.5B (10%), with ChatGPT subscriptions at 60%. Some in the chat read that as weak enterprise stickiness; others argued GPT's openness to third-party harnesses makes API share less meaningful. AWS Bedrock now requires dual L10 approval after nine-figure fraud losses—cloud users, take note. Sol's quality regression has been confirmed by multiple users over 2-3 weeks, with text processing clearly degraded. The tools section has two useful bits: WorkBuddy's polish comes from extensive steering prompts that orchestrate file display and search, which raises the bar for anyone building similar tools. Codex added cross-session task orchestration—one session monitors others and chains them by dependency order, something Claude Code doesn't support yet. And a 4×RTX 5060 Ti setup cost under $300 total, with PCIe 4.0 x4 showing no bottleneck for TP inference on Qwen models—useful if you're pricing out a local rig.

The numbers are what make this worth clicking: 10x call growth in six months, flat total AI spend, and per-session cost cut by 52%. If those figures hold up, Uber's done real engineering work on model selection and prompt compression — not just throwing more calls at the problem. But the post doesn't spell out what "70% of PRs" actually means. Is that PRs merged into main, or just PRs where an agent touched the code at some point? The first is real productivity; the second is coverage theater. No model names, no details on how agents plug into the review pipeline. I'd discount this until the full technical post is available. That said, the direction isn't surprising. Anthropic and OpenAI have both been pushing agentic coding products hard over the past year. If Uber's numbers are legit, they're among the more aggressive enterprise adopters with public data.

This piece is worth opening because Meta, Z.ai, and DeepSeek all showed the same pattern in August: the model watches a video or screenshot, calls tools to build a webpage, slides, or a mini-game, then inspects its own output. It's similar to the 2023 shift from static RAG to agentic search, but the loop direction is reversed—here the model produces first, then looks back to verify. Evaluation is changing too. Meta's WildArtifactBench ditches standard-answer scoring for pairwise comparisons and Elo rankings. On the training side, both GLM and Muse Spark 1.2 log full generate-inspect-revise trajectories as training data, so the model internalizes the loop as its own behavior. For builders, the selection criterion is shifting from static image accuracy to whether the model can complete an observe-generate-inspect closed loop. What's missing right now is closed-loop success rates in real production tasks—the three labs mostly showed curated demos.

This one's worth opening because it splits "the model got a fact wrong" into two diagnosable causes: the fact was never stored, or it was stored but couldn't be retrieved this time. Google Research's ICML 2026 paper tested 13 models on 2,150 Wikipedia facts. They built two probes: a loose one—let the model complete truncated Wikipedia text—where frontier models hit 95–98% encoding rates, meaning the knowledge is basically in the weights. Then a strict one: closed-book, four paraphrased questions (forward and reverse), all must be correct. Failure rate: 26–34%. I'd discount the absolute numbers a bit. This is a vendor paper, single Wikipedia benchmark, and any loose-vs-strict probe design will produce a gap by construction. What holds up is the shape of the gap. Cold facts and hot facts differ by only ~5 points at encoding, but the recall gap blows up to over 20 points. Cold facts aren't missing from the weights—they're just hard to pull out. The wildest finding is what thinking does. These are all single-hop facts with no reasoning chain, yet turning on thinking rescues 40–65% of encoded-but-missed facts, versus only 5–15% for never-encoded ones. A companion paper went further: replacing the thinking text with meaningless repeated sentences still helped, suggesting extra forward-pass tokens alone give the model more chances to locate stored memories. For anyone building systems, the practical takeaway is a triage ladder: rephrase the question first, then try multiple choice, then turn on thinking, and only then trigger retrieval. Don't jump straight to adding data or wiring up search every time the model gets a fact wrong. Figure out whether the shelf is empty or the key is lost.