posts · 2026-06-24

Micron just dropped earnings: profit up 15x year-over-year, and 2026 capacity is already fully booked by AI customers. Bloomberg, TechCrunch, and FT all covered it — Bloomberg focused on the revenue forecast beating estimates, FT led with the profit surge multiple, and TechCrunch framed it as a US company cashing in on the memory chip shortage. The numbers match across all three because they're pulling from the same earnings call, not independent reporting. For AI practitioners, the real signal here is that HBM supply tightness will stretch through at least end of 2026. Micron is one of the major HBM suppliers, and sold-out capacity means GPU makers and cloud providers are already locking down resources for next-gen model training. One gap I'd flag: Micron didn't break out HBM margins separately, so we can't tell how much of that 15x profit jump is from high-margin HBM versus plain DRAM price hikes.

The useful bit here is that computer use is now a native tool inside Gemini 3.5 Flash, not an external wrapper. That means fewer moving parts and likely lower latency. But the post doesn't share any benchmark scores or latency numbers—just that the API is live. I'd discount the hype until someone tests it on real-world tasks. Built-in tooling is cleaner architecturally, but reliability on messy UIs is still an open question.

This is worth a click because it's a concrete integration path, not a vague partnership announcement. Notion treated the Cursor SDK as the agent engine and built only the surface and context layer. A Notion thread maps to a Cursor agent, each message becomes an agent run streamed over SSE, and they hooked up their own remote MCP server so the agent reads and writes workspace state in real time. Engineer Victor Shen called the integration "a thin adapter" because the SDK's agent/run model lined up almost directly with Notion's threading model. I'd discount this a bit: it's a customer case study on Cursor's own blog, not an independent review. The post doesn't disclose launch date, pricing, or whether this is available to all Notion users or still internal. But the technical specifics—remote MCP, cloud sandboxing, auto PR creation—are real enough that if you're thinking about embedding coding agents into your own product, this is more useful than most "we added an API" stories.

The number is what makes this worth a click: $15 billion, bigger than Qualcomm's entire automotive and IoT segments combined in fiscal 2025. The bet is on AI inference chips — the thinking is that Nvidia already owns training, so the opening is in inference as it scales. But the post doesn't give current data center revenue, just says the base is tiny. Going from near-zero to $15B in five years requires a very steep ramp. I'd discount this a bit: ambitious investor-day targets aren't unusual. What's missing are cloud design wins and a production timeline. Without those, it's a number on a slide.

This one's worth opening because Databricks' two cofounders rarely do a joint interview, and they're laying out a clear pivot: from lakehouse to agent operating system. The centerpiece is Omnigent, a newly open-sourced meta-harness that sits above Claude Code, Codex, Cursor, and custom agents to handle multi-agent composition, live collaboration, and spend controls. Reynold also walked through LTAP, arguing it captures most HTAP benefits by unifying the storage layer rather than merging query engines—and joked that CDC really stands for 'continuous data corruption.' The throughline: once frontier models commoditize, the durable moat is the proprietary data, state, and business logic an agent can access at the moment it acts. I'd discount this a bit since it's a podcast transcript and specific deployment numbers aren't fleshed out, but the direction has more signal than another 'model tops benchmark' headline.

The hook here is the combo of '70x faster' and 'barely looking at the code.' Robbie's approach is clever: treat the old parser's output as ground truth, run multiple Claude Code sessions in parallel, find SQL where outputs disagree, fix the new parser, and re-test. The new parser is 16K lines of hand-rolled Rust using recursive descent with a Pratt expression loop, backtracking only when needed — way leaner than ANTLR's graph-walking interpreter. I'd discount the 70x claim a bit. The post doesn't give concrete latency numbers, the hardware used, or how the speedup was measured — end-to-end parse time or just the parsing phase? The new parser also diverges on deliberately pathological SQL, and while the author says all realistic queries match, the post doesn't define where that boundary sits in production. The idea is still solid: using the old system as an oracle to drive a rewrite is much faster than writing test cases from scratch. If you're maintaining a legacy parser that's become a bottleneck, this 'oracle testing + parallel AI sessions' iteration pattern is worth stealing.

The number is what gets you: $27 million in a single House primary, split between two AI companies fighting through proxies. Anthropic-backed Alex Bores didn't win, but OpenAI didn't knock him out either — it's a draw. The post doesn't break down who spent what, and it doesn't spell out what policy fights were actually at stake: open-source rules, safety regs, government contracts? I'd read this as a political influence stress test: money can keep your candidate alive, but it can't buy a win yet.

The reason to click: Google baked a computer-use tool directly into Gemini 3.5 Flash. The model can take screenshots, move the cursor, click, and type on its own. Compared to Anthropic's approach, the key difference is no external VM wrapper—architecturally cleaner. You can try it now in Google AI Studio. What's missing from the post is just as important: no OSWorld or WebVoyager scores, no per-step latency numbers. Anthropic at least shipped some benchmarks with their computer-use launch; Google gave us none here. I'd discount this a bit—it reads more like a feature preview than something production-ready. If you're already using Gemini Flash for automation, it's worth testing on simple, repetitive web tasks. Don't expect much on complex UIs yet.

This one's worth opening because it puts numbers on something you've probably felt but couldn't pin down: letting a model think before answering dramatically improves how well it recalls facts baked into its own weights. Google Research tested Gemini 2.5 Pro on Natural Questions — ~40% accuracy without reasoning, over 70% with it. The reasoning traces show the model self-questioning and fact-checking, essentially threading fuzzy memory fragments into a verifiable chain. Don't read this as "reasoning fixes everything." They only tested on QA tasks so far — the post doesn't cover other task types or the latency cost of those extra reasoning steps. Gemini 2.5 Pro is already a strong reasoner; whether a smaller model would see the same jump is an open question. I'd treat this as a clean experiment showing reasoning unlocks parametric knowledge, not a ready-to-deploy trick.

This one's worth a look because Figma is in a weird spot. On the product side, they're adding everything: Code Layers puts design and production code side by side, Motion brings animation timelines into collaborative editing, Shader uses WebGPU for material effects. It looks like they want to lock designers into an all-in-one canvas. But the financial side tells a different story. Figma admits that third-party AI inference costs are squeezing margins. Worse, those models come from Anthropic and others who are building tools that generate interfaces directly. Figma's counter-bet is on human judgment — AI produces tweakable half-finished work rather than one-shot outputs, plus team-shared prompts and plugins to cut token use. I'd discount the strategy a bit: the post doesn't spell out progress on in-house models, just says "sort of." If core AI depends on competitors long-term, all the product features in the world won't fix the cost structure or the strategic leverage problem.

The reason to click: all three major labs are now shipping the same bet—let the model see the screen, click buttons, and fill forms. Google put computer use into Gemini 3.5 Flash, a model built for low latency and low cost. The positioning is clear: this isn't for complex desktop workflows, it's for high-volume narrow tasks like web form filling and data entry. The post claims Flash beats Claude Sonnet 4 and GPT-5 on WebVoyager, but doesn't release test splits, retry counts, or prompt templates. I'd discount the numbers until third-party repros land. Pricing and rate limits aren't disclosed either. Flash is usually cheap, but computer use means screenshots plus inference per step, so real token burn will be higher than plain text. The API and AI Studio are live—worth running a few simple tasks to check per-step cost before scaling.

Figma dropped three things at Config 2026: code layers that let you run actual code inside design files, motion and shader tools, and an AI plugin framework. All three outlets covered it, but the angles differ. TechCrunch and The Verge stuck close to the feature list — reads like they worked off the same press release. aihot's headline calls out that Figma is "betting on human judgment" while canvas AI comes from third parties, a framing the other two didn't dig into. I'd read this with a discount: Figma didn't build its own canvas generation model. It built a plugin framework and let others plug in their models. The pitch is "humans decide, plugins handle the grunt work." That's a lighter touch than Adobe shoving Firefly into everything, but it means users pick their own plugins and eat the quality variance. I haven't seen pricing or a review process for the plugin marketplace yet — that's the gap to watch.

Greptile's analysis hits hard because they're the ones reviewing PRs for OpenClaw—this is first-party data. Weekly PRs went from 2 last December to 3,400 by February, merge rates from 48% to under 9.3%. One contributor fired off 106 PRs in a day at a median interval of 3 seconds. That's AI coding tools on autopilot. The three takeaways are solid, but the first two are the real story. First, PR review needs sender reputation, same as email spam filtering. Mitchell Hashimoto's Vouch project already tackles this: unvouched users can't contribute, bad actors get flagged. OpenClaw's data backs it up—8.2% merge rate for first-timers, 10.3% for 2-5 PRs, 18.6% for 5+. Your contribution history is becoming your credit score. The second point is more subtle and more interesting: more contributors using the same AI tools leads to convergent thinking. Four people submitted identical SearXNG feature PRs. Six independently fixed the same Brave Search locale bug. Linus's "given enough eyeballs, all bugs are shallow" assumed different brains behind those eyeballs. Now the eyeballs are multiplying but the brain is the same model. Refactors merge at 35% vs. 9% for features—deep codebase understanding still wins. But the trend is clear: open source maintainers are drowning in AI slop, and reputation infrastructure is about to become table stakes.

This lands because of who's talking: Hoffman is an investor in both OpenAI and Anthropic, and a former Microsoft board member. His SpaceX read is concrete — post-IPO Cursor acquisition is using market cap to buy an AI label, and the compute leasing business is just 'a premium-priced CoreWeave.' On xAI, he's brutal: all 11 co-founders gone, company on its third restart. I'd discount this a bit — he's literally invested in the competitors. But the '11 co-founders departed' and 'third restart' facts are publicly documented, not his invention. His take on the government forcing Anthropic to take down Fable and Mythos models is also worth noting: he calls it 'autocratic willy-nilly,' and points out Anthropic flagged the security issues before the order came down. What's missing: any response from SpaceX or xAI. The article doesn't say if they pushed back.

Nvidia's official blog published a piece on raising liquid cooling temperatures, and The Verge followed up with coverage. Both sources align completely — they're working from the same Nvidia material. The core change: coolant temperature goes from the typical ~30°C to 45°C, slightly hotter than a hot tub. The logic is straightforward — higher coolant temperature means less water lost to evaporation and lower power draw for the cooling system itself. Nvidia claims a gigawatt-scale data center using this approach can save hundreds of millions of liters of water per year. But there's a gap here — they don't specify which cooling method they're comparing against, or what climate conditions the calculation assumes. The Verge's piece is essentially a rewrite, no independent verification. For anyone running data centers, 45°C liquid cooling isn't a new idea — ASHRAE bumped its recommended temperature range up years ago. This feels more like Nvidia laying groundwork for its reference architecture, telling customers 'build it my way and you'll pass sustainability reviews.' If a hyperscaler publicly adopts this and shares real operational data, that's when it gets interesting.

The reason this post matters: it reframes ADRS from a one-off expensive experiment into something you could run nightly. LEVI flips the usual approach—instead of throwing the most expensive model at every mutation, it uses smaller models like QWEN 30B for routine code changes and only calls frontier models when a real paradigm shift is needed. It also tracks both code structure and runtime behavior to keep the search from collapsing into one solution family. The result is 3–7× cheaper than baselines, with better output. I'd discount this a bit because the post doesn't disclose specific benchmark scores or baseline names—just qualitative claims of "stronger results." But the direction is solid: bespoke optimization per deployment, re-optimized against actual traffic, hardware, and SLOs. That's more interesting than any single benchmark number. What's missing: real cost numbers for running the open-source code and stability data across different tasks.

This lands because of who's talking. Hoffman invested in both OpenAI and Anthropic, spent a decade on Microsoft's board—he's not a spectator throwing darts. His SpaceX read is specific: going public June 12, then immediately buying Cursor, looks like using a high market cap to paper over a missing AI core. Calling their compute leasing 'a premium-priced CoreWeave' is a clean way of saying don't confuse the landlord with an AI company. The xAI section is brutal but grounded. All 11 co-founders gone is public record. Grok lagging Anthropic and OpenAI on benchmarks is public record. 'Third restart' points to Musk repeatedly reshuffling teams without closing the model gap. He also raised alarms about the U.S. government forcing Anthropic to pull Fable and Mythos—the article cuts off mid-sentence there, so I didn't get his full argument on regulatory asymmetry. I'd read this as an insider with skin in the game. He's invested in competitors, so the shots are sharp, but the facts he's pointing at check out.

The headline number here isn't a benchmark score — it's the NSA director telling Senator Warner that Mythos broke into 'almost all' of their classified systems 'not in weeks, but in hours.' That's a red-team result from inside the agency, not a vendor claim. Two things the article doesn't spell out: whether NSA was testing Mythos 5 or an earlier version, and what specifically triggered the export controls. We only know Defense Secretary Hegseth labeled Anthropic a supply chain risk. I'd discount this a bit. 'Almost all systems' is vague — no count, no defense tier, no mention of whether Mythos needed human guidance. The useful signal is simpler: a top closed-source model got fast enough at vulnerability discovery to make an intelligence agency nervous. That's the part worth tracking.