Signal or Noise
We run through the week's AI headlines and make the call: is this actual signal worth paying attention to, or just noise clogging the timeline?
Real talk. Unpopular opinions. No hype. Two builders cut through the AI hype cycle every week — and call it like it is.
Hosted by Oscar Gallo & Matt Wozniak
EP 23 · September 15, 2026 · 71 min
In machine learning, “human in the loop” means a human who provides oversight and feedback in an automated system. That’s the lens of this show: AI is powerful, but humans aren’t leaving the loop. Not yet. Maybe not ever.
This isn’t another “AI is going to change everything” podcast. It’s for builders, operators, and the AI-curious who are tired of breathless hype, doomerism, and surface-level news recaps with no original thought.
We run through the week's AI headlines and make the call: is this actual signal worth paying attention to, or just noise clogging the timeline?
A real use case or product idea lands on the table. We debate whether it's worth building now or if the tech isn't there yet.
Take a complex AI concept and explain it the way you'd actually explain it to a non-technical stakeholder. No jargon allowed.
One tool, library, or workflow change we actually adopted this week. No sponsorship energy. Just what's in the trenches.
AI Engineer & Entrepreneur
AI Engineer and entrepreneur. He lives in the intersection of engineering and businesses.
Serial Builder & Relentless Executor
Serial Builder and relentless executor. He comes from the lens of what works and what doesn't.
Meta launched Muse Code, a terminal coding agent designed to work across large repositories, coordinate background agents, recover after crashes, and keep going for hours. Is this a better coding system or simply more automation to review?
Oscar and Matt look past the model benchmark and examine the operating system around Muse Code. Persistent workers use isolated worktrees. A local event log records model calls, approvals, edits, and tool use. Meta says one kernel-optimization run made more than 1,000 tool calls over as long as 24 hours.
The core question: what changes when agents persist for hours, survive crashes, and coordinate other agents without waiting for you?
Released August 5 in beta for macOS and Linux, Muse Code is a terminal coding agent built for long jobs across large repositories. It launches persistent background agents, splits work across isolated worktrees, and leaves your working copy untouched until changes are ready to review. The durability is the real advance: an append-only local event log of approvals, model calls, edits, and tool use lets it reconstruct a session after a crash instead of starting over. Meta co-trained Muse Spark 1.2 with the harness and demonstrated more than 1,000 tool calls across GPU-kernel optimization runs lasting as long as 24 hours.
On August 1 OpenAI published ten results spanning high-dimensional geometry, coding theory, group theory, operator algebras, quantum complexity, lattice cryptography, and extremal combinatorics. An internal version of Astra generated the arguments, humans prepared the manuscripts with the model, and the model formalized each argument in Lean. OpenAI shipped a 249-page paper, reasoning walkthroughs, and machine-checkable certificates, and estimates the successful runs cost about $2,000 in tokens. Lean can confirm a proof follows from its stated assumptions; it cannot confirm the formal statements match the original research questions or that the claimed novelty survives expert review. Signal pending outside review.
V4 Flash entered public beta on July 31 with the same 284 billion-parameter mixture-of-experts architecture as the preview and 13 billion active parameters, but new post-training aimed at agent work. It supports a 1 million-token context window, thinking and non-thinking modes, tool calls, and both OpenAI-compatible and Anthropic-compatible APIs. Listed pricing is $0.14 per million uncached input tokens and $0.28 per million output tokens, with published setup guides for Claude Code, GitHub Copilot CLI, and OpenCode. Cheap enough to test inside a real agent loop without rewriting the harness.
Axios reported on August 4 that the White House finalized a voluntary pre-release review framework under the June 2 executive order, including a classified cyber benchmark and up to 30 days of government access to a covered model before it reaches other trusted partners. Per people briefed on it, a covered model must be closed-source, state of the art, and present national-security risks, and open models are excluded. Neither the framework text nor the capability thresholds are public, so the carve-out comes from reporting on a closed industry briefing rather than a published document. The policy creates different review paths based on how weights are distributed.
Google announced its largest AI leadership change since the Brain and DeepMind merger on August 5. Hassabis leaves the Google DeepMind CEO role but stays at the company as DeepMind chair and Alphabet chief scientist while continuing to lead Isomorphic Labs. Jeff Dean is leaving after 27 years to start a company focused on AI and scientific discovery, with Google investing. CTO Koray Kavukcuoglu becomes senior vice president reporting directly to Sundar Pichai, and no replacement CEO was named. Signal, but not yet a product signal: the evidence is research retention, Gemini release quality, and whether decisions move faster.
Oscar“A coding agent is not ready for long, unattended work unless it can reconstruct every action after a crash. Durable state and an audit trail matter more than another benchmark win.”
Matt“Everyone is calling this a light touch. Voluntary, relax. I have never seen a government program stay the size it started. Thresholds move. Thirty days becomes sixty. And the countries we are actually racing are not running this process and never will. We are building a very careful system for arriving second. Every day of review is a day of lead, and nobody is counting the bill.”
AI made engineers faster. It did not make companies faster at deciding what to build. That is now the hard part.
Mike Lyons and Greg Pfister of KaiRise join Oscar and Matt. The conversation starts with a $4.3 million voter registration system that shipped on time, on budget, and on scope. Users still rejected it. The team built what was requested, but not what people needed.
AI makes that risk bigger. Teams can produce more software in less time. Leaders still need to set direction. Product teams still need to understand customers. Someone still has to decide when to stop.
If writing the code was never the whole job, making it faster does not make the company faster. The slow part moved to everything around engineering — direction, decisions, approvals.
Annual budgets and long approval chains were designed for teams that delivered slowly. When delivery compresses, the planning cycle becomes the constraint.
Formal Agile roles are in decline. The underlying principles — short feedback loops, working software, real customer contact — did not stop mattering.
A live prototype settles in one meeting what a requirements document argues about for a month. Building got cheap enough to make showing the default.
Estimation assumed human hours. Points, lines of code, and token usage all measure output, and none of them prove a customer got value.
The scarce ability after AI is not producing more. It is recognizing the point where more code stops improving the outcome.
Unclear ownership, misaligned incentives, and teams shipping features nobody asked for are structural. No model fixes them.
Kimi K3 got hot enough to trigger a U.S. ban debate. If Washington restricts a model you can download and run yourself, is that national security, closed-model protection, or both?
Oscar Gallo and Matt Wozniak cut through the week's real AI stories.
Your CEO says, “We need AI.” Before you hire an AI engineer or buy another tool, find one painful process worth fixing.
Episode 15 is our first Dear Human in the Loop, an advice episode for founders, engineering leaders, developers, and decision-makers trying to make practical AI calls.
Start with problems, not prompts.
Hire for your biggest business problem, not the trendiest job title.
Show developers real value and give them time to learn. Trust beats mandates.
Learn engineering fundamentals, system design, product thinking, communication, and critical thinking. Model quirks will expire.
Apple says OpenAI built its hardware program with stolen trade secrets. OpenAI denies any interest in Apple's secrets. We make the Signal or Noise call.
Oscar“The Apple lawsuit is a warning for every AI company hiring from a competitor. Talent does not arrive empty-handed. If your onboarding process does not separate experience from confidential material, your product roadmap can become evidence.”
Matt“I don't care if your model is as good as Fable. If it's close, and it's faster, and it's cheaper — it wins. The whole industry is selling you a god-tier model like it's the finish line, but with orchestration and model routing, you don't need one genius doing everything. You need a smart conductor and a cheap, fast bench. The frontier model is becoming the part you use least — and the teams still paying premium tokens for every keystroke are going to feel really dumb in a year.”
New episodes every week. Reply with the story you want us on next.