PM Lead Pro
Podcast/AI digest №11/2026-10-15

AI Digest, Oct 15: Code Review Bottleneck, Financial Agents, Small AI

Why 741% more AI-written code yields only 20% more shipped software, how approval fatigue affects financial agents, and why small AI may matter for developing economies.

Listen7:20
  1. PM Lead Pro · intro
  2. AI Rocket or Traffic Jam
  3. Code Review Bottleneck
  4. Financial Agents and Approval Fatigue
  5. Deterministic Controls and Classifiers
  6. AI Proves Math with Lean
  7. Small AI for Developing Economies
  8. Cortex and Parametric Memory
  9. Takeaways and Closing Thought
Download

Daily AI digest by PM Lead Pro: a conversation of NotebookLM hosts on the day’s sources.

Today’s sources:

Podcasts

Articles and research

China

Pages we track (changes of the day)

Facts are the hosts' summary of the day's sources listed on this page; check the original before quoting. The PM Lead Pro notes are generated (text by Claude, voice by Gemini) and approved by the author.

Transcript

PM Lead ProThis is PM Lead Pro. Today's digest asks whether AI is speeding your team up or just moving the queue: code review, financial agents, formal math proofs and small AI.

Welcome to this deep dive. You know, you're probably integrating AI into your team right now to, well, to move faster, right?

Yeah, it sounds amazing on paper.

I mean, it's like strapping a rocket engine to your car.

Exactly.

But what if that rocket is actually like driving you straight into a massive traffic jam?

That is a very real risk we're seeing right now.

So today we're pulling from a huge stack of sources. We've got the Agent Report, NBER, the World Bank, and a really fascinating brief on Chinese AI.

AI. And we're going to explore the AI coding bottleneck, swarms of financial agents, a pure

math breakthrough, and this concept of small AI. Yeah, and our whole mission today is just cutting

through the hype. We want to figure out how to actually ship value with AI, not just generate

noise. Right. So let's start with that traffic jam from the agent report and NBER. Yeah, so say your

developers are using AI tools. The data shows lines of code are just jumping by a staggering 741%.

Which sounds incredibly productive until you look at the output.

Right, because actual shipped software is only up 20%.

So where is all that extra code going?

Well, it's just sitting in merge queues.

The NBER data shows the time it takes to review and approve code has lengthened by 49%.

Wow.

Yeah, that adds almost three and a half extra days to a cycle.

I mean, writing code was never the real constraint.

Reading and verifying it is.

Okay, wait, I have to push back here, though.

If an AI is smart enough to generate the code why can we just prompt it to you know review its own work Mostly because of silent failures Okay If you let an AI review its own massive output without a secondary check Right it might miss its own blind spots

Exactly.

You risk shipping vulnerabilities at light speed.

Despite all these tools, humans are still writing 77% of the code review comments.

So we are the ultimate bottleneck.

Yeah, we are.

Man.

PM Lead ProTakeaway for team leads: lines of code rose 741%, but shipped software only 20%. Review time grew 49%. Track shipped output and review capacity, not code volume.

Okay, now project that bottleneck onto fully autonomous enterprise systems.

According to Third Moment Research, they're running 10,000 agents concurrently for up to 48 hours in quantitative finance.

Which is just a staggering volume of actions.

Right. And you can't possibly have a human reviewing every single trade there.

It's like, you know those terms of service pop-ups on websites?

Oh yeah, where you just blindly click accept.

Exactly. Eventually you get so overwhelmed by the volume you just click accept without reading.

Well, hedge fund Two Sigma actually calls that exact phenomenon approval fatigue.

Approval fatigue, huh?

Yeah. Forcing a human to click approve on every single AI action doesn't just limit your scale, it creates massive risk.

Because that human safety net basically just stops paying attention.

Exactly. So the solution is building deterministic controls outside the model entirely.

Oh, so instead of asking the AI to police itself, you build a traditional hard-coded filter.

Right, an auto mode classifier. It automatically approves the routine, low-risk tasks and only flags the highly ambiguous edge cases for a human.

So you need brakes, not to stop, but just so you can drive fast safely.

Yeah perfectly put And if traditional software needs those hard brakes we seeing a fascinating divergence in fields that require absolute precision Like pure mathematics Right

PM Lead ProFor owners deploying agents: approving every action creates approval fatigue. The discussion suggests deterministic controls outside the model, with a classifier that passes routine tasks and flags ambiguous cases to a human.

Our brief on Chinese AI research notes that the Shanghai AI Lab used their Intern S2 model to help prove the 3D geese conjecture.

Which is a major dynamical systems problem.

And the crazy part is they didn't just ask a chatbot for the answer.

No, they plugged the model into Peking University's Sheaf framework.

Right. And it generated 550,000 lines of Lean code in just five days. And Lean isn't like Python or something.

No. Lean is a formal verification language. It basically turns abstract math into software that absolutely must compile.

So if there is a single logical flaw?

The code simply fails to run. The system mathematically proves its own logic.

By doing this, they completely eliminated the human review errors we see in standard software engineering.

That is wild. But this level of automated reasoning isn't just for hedge funds and elite math labs.

Not at all. It's about to hit the broader global economy.

Right. Because research from CEPR shows human capital, skills and education, drives up to 70% of income differences between countries.

And the World Bank's 2026 report argues AI is the ultimate bridge for that gap.

But developing nations don't need these trillion parameter frontier models running in massive data centers.

Exactly. They need small AI. Models adapted to basic phones via text and voice to scale expert knowledge instantly.

It kind of like how developing nations skipped landlines entirely and went straight to mobile phones but for cognitive skills That a great analogy Which actually ties perfectly into our model radar today Look at Google Times FM and Tab and so on

and so on.

But for one three hundredth the cost of traditional methods.

Oh wow.

So you could run that affordably to send a farmer a hyperlocal forecast over an SMS text.

Exactly.

And finally for running complex tasks on local devices we have a whole new class of model

called Cortex.

Right because normally an AI's memory is just the prompt window which is like trying

to memorize a textbook while you're holding it open.

Yeah but Cortex uses parametric memory.

It learns on the fly actually updating its own internal wiring, its weights.

So it remembers context natively without needing massive computing power.

Exactly. So for you listening today, the practical takeaway is this. Do not measure your team's AI success by volume.

Right, not by lines of code.

Measure the actual shipped output. And please, implement classifiers so you don't burn out your team with approval fatigue.

Great advice. And I'll leave you with this to chew on.

If small AI allows developing economies to leapfrog traditional education barriers,

will the future center of global human capital shift entirely away from the West?

It's a huge question.

It really is.

Maybe that AI rocket engine isn't just making us faster.

Maybe it's taking us somewhere completely different.

PM Lead ProMore at pmlead.pro: the transcript and sources are on the episode page. Question for you: where is the queue in your team right now, writing, reviewing or approving?

Discussion