WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-03-18 1 00:00:00.000 --> 00:00:06.530 Good morning and welcome to Builder's Briefing for March 18th, 2026. I'm Alex, joined as always by Sam, and we've got a packed show today. The headline is Mistral dropping a tool that doesn't just write your code — it mathematically proves your code is correct. 2 00:00:06.530 --> 00:00:13.385 Yeah, that one had me doing a double-take this morning. We've also got a Jepsen report you need to read before your next MariaDB upgrade, the Xbox One finally getting hacked after thirteen years, and Kagi adding LinkedIn Speak as a translation language, which — chef's kiss. 3 00:00:13.385 --> 00:00:22.116 Alright, let's get into the big story. Mistral released Leanstral — an open-source agent built specifically for formal proof engineering in Lean 4. This is not your typical coding copilot. It constructs and verifies mathematical proofs of correctness for the code it writes. Over four hundred points on Hacker News and the discussion is substantive. 4 00:00:22.116 --> 00:00:29.697 Okay, so for folks who haven't touched formal methods — this is the difference between "my tests pass" and "I have a machine-checked mathematical guarantee that this property holds." Like, if you're writing financial settlement logic or cryptographic primitives, tests can miss edge cases. Proofs can't. 5 00:00:29.697 --> 00:00:36.952 Exactly. And the key shift here is accessibility. Lean 4 has been maturing quietly, but the barrier to entry used to be basically a PhD in type theory. Leanstral drops that to "willing to learn the tooling." You can pair it with your existing CI pipeline and get machine-checked invariants. 6 00:00:36.952 --> 00:00:45.859 That's interesting because I've been watching the formal methods space for years, and it's always been this thing where academics love it and industry says "too expensive, too slow." But if an AI agent handles the proof construction, the cost-benefit math completely changes. An order of magnitude cheaper verification — that's the claim, and I believe it. 7 00:00:45.859 --> 00:00:51.087 And the signal here is clear: expect every major model provider to ship proof-oriented tooling within the year. The frontier of AI-assisted dev is moving from "write code faster" to "write code you can trust." 8 00:00:51.087 --> 00:00:56.016 If you've been dismissing formal methods, this is genuinely the moment to reconsider. Smart contracts alone — think about how much money has been lost to bugs that a formal proof would have caught. 9 00:00:56.016 --> 00:01:00.920 Moving to other AI news — MiroThinker-H1 just scored eighty-eight point two on BrowseComp, which is the benchmark for complex web research and prediction tasks. Deep research agents keep climbing. 10 00:01:00.920 --> 00:01:06.999 Right, and what's wild is this is an open contender. If you're building research pipelines or anything that synthesizes info from multiple web sources, you now have a real alternative to proprietary deep research APIs. The gap is closing fast. 11 00:01:06.999 --> 00:01:12.903 There's also a marketing skills pack for Claude Code that caught my eye. It gives your Claude Code agent CRO, copywriting, SEO, and growth engineering capabilities. So your AI pair programmer suddenly understands conversion funnels too. 12 00:01:12.903 --> 00:01:19.183 That's a big deal for solo founders especially. You're not just getting an engineer anymore — you're getting an engineer who can think about the business side. It ties into the broader trend of domain-specific skill layers on top of foundation models. 13 00:01:19.183 --> 00:01:27.364 Over in developer tools, a couple things worth flagging. First — Oxyde, a Show HN project. It's a Pydantic-native async ORM with a Rust core underneath. If you're building Python APIs and you're tired of SQLAlchemy's complexity, this pairs your Pydantic models directly with your ORM layer and gives you real async performance. 14 00:01:27.364 --> 00:01:32.618 Oh, I love this pattern — Pydantic models that double as your ORM layer? That's the kind of developer experience win that actually reduces bugs. Less mapping between layers means less surface area for mistakes. 15 00:01:32.618 --> 00:01:39.548 And then there's Avery Pennarun's piece arguing that every layer of review makes you ten times slower, and the math is compelling. He shows how approval layers compound latency in shipping. Required reading if you're a technical leader trying to cut ceremony from your process. 16 00:01:39.548 --> 00:01:44.877 I've lived that. Three layers of PR review, staging gates, approval workflows — and suddenly a one-line fix takes a week to ship. It's concrete ammunition for the "trust the team" argument. Link's in the briefing. 17 00:01:44.877 --> 00:01:52.007 On the infrastructure side, two big ones. Meta published a deep dive on recommitting to jemalloc as their primary memory allocator. If you run memory-intensive services — caches, ML inference, databases — jemalloc remains the production-grade choice over mimalloc or tcmalloc at scale. 18 00:01:52.007 --> 00:01:58.962 And then Jepsen tested MariaDB Galera Cluster twelve-point-one-point-two. Kyle Kingsbury strikes again. If you're running Galera in production, please read the findings before your next upgrade. Jepsen reports have a habit of surfacing the bugs your monitoring will never catch. 19 00:01:58.962 --> 00:02:02.064 Also FFmpeg eight-point-one landed — if you process any media in your pipelines, check the changelog for codec improvements. 20 00:02:02.064 --> 00:02:07.818 Alright, security story of the day — the Xbox One, released in 2013, marketed as basically unhackable — its entire security chain has finally been broken via hardware-level voltage glitching. Unsigned code runs at every level now. 21 00:02:07.818 --> 00:02:14.749 Thirteen years! That's actually an impressive run. But the lesson for anyone building embedded devices is sobering — voltage glitching will eventually defeat even well-designed secure boot chains. Given enough time and motivation, hardware security is a delay, not a guarantee. 22 00:02:14.749 --> 00:02:18.351 Time for quick hits. Kagi Translate added LinkedIn Speak as an output language, and honestly that's the most internet thing I've heard all week. 23 00:02:18.351 --> 00:02:21.053 "Thrilled to announce that I am humbled to share my synergistic learnings" — yeah, peak internet. I love it. 24 00:02:21.053 --> 00:02:27.883 Tabler Icons hit fifty-nine hundred free MIT-licensed SVG icons. VictoriaMetrics is trending again as a fast Prometheus alternative. The classic "Build Your Own X" repo is surging with ten thousand plus engagement — still the gold standard for learning by reimplementation. 25 00:02:27.883 --> 00:02:32.712 Oh, and someone rebuilt Monkey Island from the ground up for the Commodore 64, and the SEC might scrap quarterly reporting — which could totally reshape fintech data products. Wild range today. 26 00:02:32.712 --> 00:02:39.216 So here's today's through-line. AI tooling is graduating. It's moving from "write more code" to "write provably correct code" with things like Leanstral, and "do non-engineering work" with domain-specific skill packs. The moat isn't in code generation anymore. 27 00:02:39.216 --> 00:02:45.821 Right. The moat is in verification and domain-specific capabilities layered on top of foundation models. If you're building AI features, invest your time in formal methods tooling and crafting domain-specific agent skills — not chasing the next base model upgrade. 28 00:02:45.821 --> 00:02:49.474 That's the briefing for March 18th. All the links are in the show notes. If any of this changed how you're thinking about your stack, let us know. 29 00:02:49.474 --> 00:02:51.000 Go prove some code correct this week. We'll see you tomorrow.