WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-03-04 1 00:00:00.000 --> 00:00:07.157 Hey everyone, welcome to the Builder's Briefing for March 4th, 2026. I'm Alex, joined as always by Sam. We've got a packed one today — WiFi that can see you without a camera, Apple's M5 lineup, a Donald Knuth paper on Claude's reasoning, and Meta's smart glasses privacy mess getting worse. 2 00:00:07.157 --> 00:00:12.290 Yeah, today's got a real theme running through it. Edge sensing, camera-free intelligence, privacy tailwinds — it all connects in a way that I think is going to click for a lot of builders. Let's get into it. 3 00:00:12.290 --> 00:00:20.952 Alright, the big story. RuView just open-sourced a system that does real-time human pose estimation, vital sign monitoring, and presence detection using nothing but commodity WiFi signals. No cameras, no wearables. It reads the channel state information — basically the signal distortion patterns your body creates — and maps that to full body meshes. 4 00:00:20.952 --> 00:00:26.382 This is wild to me because the hardware requirement is literally a WiFi router. That's it. The repo already has over twenty-five thousand engagements, which tells you developers have been waiting for something like this. 5 00:00:26.382 --> 00:00:31.515 Right, and think about the use cases. Elder care, smart home, fitness tracking, security — all of it without a single camera. The privacy angle is enormous. You completely sidestep the camera consent problem. 6 00:00:31.515 --> 00:00:40.424 And the deployment cost is effectively zero because WiFi is already in every building. If you're building anything with spatial awareness, you should be prototyping with this now. The sensing layer is disaggregating from the camera, and WiFi and RF-based perception are becoming first-class inputs for AI. Link in the briefing if you want to check out the repo. 7 00:00:40.424 --> 00:00:49.357 Okay, shifting to AI infrastructure. A couple things caught my eye. First, LMCache — if you're self-hosting LLMs and hitting latency walls, this is a dedicated KV cache layer that sits between your inference engine and memory. For multi-turn conversations where you're recomputing key-value pairs every time, this is the difference between a demo and production. 8 00:00:49.357 --> 00:00:57.501 That's the kind of boring plumbing that actually matters. Along those same lines, someone posted a full architecture walkthrough for building a voice agent with sub-five-hundred-millisecond latency end to end. Real measurements, not vibes. If you're fighting that 'talking to a robot' feeling, this is your reference architecture. 9 00:00:57.501 --> 00:01:06.213 And for the agent builders — AgentScope dropped alongside a companion project called ReMe. AgentScope gives you actual observability into what your agents are doing and why, and ReMe handles the memory layer with explicit remember and refine cycles. If your agents are forgetting context or hallucinating from stale memory, these are targeted solutions. 10 00:01:06.213 --> 00:01:13.765 Can we talk about the Knuth paper? Donald Knuth — the Donald Knuth — published a formal analysis of cyclical patterns in Claude's reasoning. He's calling it 'Claude's Cycles.' If you're doing any kind of prompt engineering or evals, this is rare formal computer science analysis of how LLMs actually think. 11 00:01:13.765 --> 00:01:18.676 Yeah, and ironically, Claude dot ai was experiencing elevated errors today. Which is your regular reminder — build fallback model routing into your inference layer. Don't hard-code a single provider. 12 00:01:18.676 --> 00:01:19.786 Learned that one the hard way more than once. 13 00:01:19.786 --> 00:01:28.671 On the dev tools side, here's a fun one — Tobi Lütke, yes, Shopify's Tobi, put out qmd. It's a local-first CLI search engine for your docs and knowledge bases. Runs entirely on your machine, tracks current state-of-the-art retrieval approaches. If you're drowning in markdown and meeting notes, this makes them queryable without shipping anything to the cloud. 14 00:01:28.671 --> 00:01:36.864 I love that it's local-first. That fits the whole theme today. There's also a cautionary tale worth mentioning — an open-source maintainer shared how SEO spam and AI-generated content are literally burying his actual project page in search results. If you maintain an OSS project, invest in discoverability now before it gets worse. 15 00:01:36.864 --> 00:01:40.393 That one hit home for a lot of people, I think. Alright, hardware news — Apple shipped the M5 Pro and Max MacBook Pros, plus an M5 MacBook Air. 16 00:01:40.393 --> 00:01:47.328 For builders, the spec to watch is the unified memory bump. Larger local models, faster compilation, better on-device inference. The M5 Max memory bandwidth is going to matter a lot if you're running local LLMs. And honestly, the Air with M5 is now a legit portable AI dev machine. 17 00:01:47.328 --> 00:01:52.831 Also worth noting — ARM's Cortex X925 is reaching desktop-class performance. So your on-device inference workloads are getting more viable on ARM-first hardware without the cloud round trip. Everything's moving to the edge. 18 00:01:52.831 --> 00:01:55.398 Which ties right back to the WiFi sensing story, right? Edge compute, edge sensing, no cloud dependency. 19 00:01:55.398 --> 00:02:01.271 Exactly. Now, security and privacy. Meta's smart glasses are generating serious backlash. Workers are saying 'we see everything' — reports of extensive data collection. If you're building on Meta's AR platform, expect regulatory friction. 20 00:02:01.271 --> 00:02:06.577 This is where the RuView story becomes even more relevant. Camera-free sensing isn't just a nice-to-have, it's becoming a competitive advantage because of exactly this kind of backlash. The privacy tailwind is real. 21 00:02:06.577 --> 00:02:12.327 And one more — Ars Technica fired a reporter over AI-fabricated quotes in published journalism. If you're building content tools or AI writing assistants, verification layers are not optional. Your users will get burned without them. 22 00:02:12.327 --> 00:02:16.054 That's a sobering one. The 'just ship it and let the AI generate everything' approach has real consequences when the output is wrong and nobody checks. 23 00:02:16.054 --> 00:02:24.371 Quick hits before we wrap up. British Columbia is permanently adopting daylight saving time — update your timezone libraries. There's a debate raging on Hacker News about not becoming an engineering manager, the classic IC versus management track argument. And physicists are building a fully open-source quantum computer, which is cool. 24 00:02:24.371 --> 00:02:27.604 The timezone one is the kind of thing that silently breaks production systems six months later. Seriously, check your dependencies. 25 00:02:27.604 --> 00:02:34.366 So here's the takeaway for today. The sensing and inference layers are moving to the edge and going camera-free. WiFi pose estimation, sub-five-hundred-millisecond local voice agents, local-first doc search, Apple's M5 memory bandwidth — it all points in the same direction. 26 00:02:34.366 --> 00:02:40.313 And if you're building agents, invest in observability and memory management before you try to scale. AgentScope, ReMe, LMCache — they're all solving the 'works in demo, breaks in production' problem. That's where the real work is right now. 27 00:02:40.313 --> 00:02:43.817 Prototype with non-camera sensors, build for on-device inference, and the privacy tailwinds will reward you. That's the bet to make right now. 28 00:02:43.817 --> 00:02:45.397 Agreed. The future is sensing without seeing. Love that framing. 29 00:02:45.397 --> 00:02:48.605 That's the Builder's Briefing for March 4th. All the links are in the briefing notes. We'll see you tomorrow — go build something. 30 00:02:48.605 --> 00:02:49.000 Later, everyone!