DeepMind AI code review: write prompts with a one-sentence check

October 14, 2026 · 11 min · Free, with full transcript

AI writes roughly three quarters of Google DeepMind's production code, yet only about one change in eight is fully handed to the AI. What does that mean for how you prompt? The episode argues that reliability comes from scoping and review, not from the model or magic phrases, and that delegation works best on well-defined, verifiable tasks. You will be able to write a one-sentence check before writing a prompt, split vague tasks, and use Google's Gemini Argon tips such as grill-me questions and AGENTS file retrospectives. You also get Wharton findings on threats, tips and chain-of-thought, a 20-input test set method, few-shot prompting, prompt caching, and Asana's measurable-target example.

Listen to the podcast

11 min

Chapters

Key takeaways

  • Write the check before the prompt: if it fits in one sentence delegate, if it needs a paragraph split the task, and if you cannot write it use the model as a sparring partner.
  • Ask the model to interview you with clarifying questions before it starts, and have it pause before irreversible steps like deleting, sending or paying.
  • After a bad session, have the model review where things stalled and update your saved standing instructions.
  • Stop threatening or tipping the model, and test prompt changes on about twenty real past inputs before picking a winner.
  • Put static material like style guides, policy and examples at the top of the prompt and the changing question last to enable caching.
Read the full transcript

Host:This is MBA Training. On the table: 88 percent of DeepMind's AI code changes still need human review, so write prompts that can be checked. Picture a Michelin kitchen where the robot cooks three plates out of four, and the head chef still tastes every single one at the pass before it goes out.

Expert:That's Google DeepMind, more or less. And the tasting is the part everyone skips when they quote the headline.

Host:The headline being "AI writes most of Google's code."

Expert:Roughly three quarters of production code, yes. A DeepMind research scientist, Haydn Belfield, published the internal numbers this week. People read that line and stop. Wrong place to stop.

Host:Fine. I'm keeping reading. What's under it?

Expert:Only about one code change in eight is fully handed to the AI. The other seven need human oversight. And even that lucky one gets a human look before it ships.

Host:Wait, what? So the robot cooks, but it basically never gets the restaurant to itself.

Expert:Never. And that's what I want to tear apart today, because this little report is the best prompt-engineering document of the year, and it doesn't contain a single magic phrase.

Host:Oh, come on, no "you are a world-class senior engineer"?

Expert:Not one. Which tells you how much that line was ever worth.

Host:Okay, teardown. Piece by piece. Start with the part that works.

Expert:What works is where the automation lands. They surveyed senior DeepMind researchers, and delegation runs highest on well-defined, verifiable tasks. Verifiable meaning somebody can check the answer cheaply, like a test that passes or fails. It runs lowest on open-ended scientific ideation, the "come up with a new idea" stuff.

Host:Which is exactly the stuff people want to hand off.

Expert:Exactly the stuff. Everyone wants the model to write the strategy. The lab with one of the strongest models on earth lets it fix the plumbing.

Host:Quick aside, since we're on that model. The Neuron reported Google opened Gemini 4 Argon to paid developers through the API, the plug-in point where apps talk to the model, around the thirteenth or fourteenth. Pro and Ultra subscribers got it in the Gemini app too.

Expert:With an introductory price that doubles once November ends.

Host:Doubles. That's a "teaser rate" move. Very mortgage-broker of them.

Expert:Which is relevant, because a sloppy prompt that needs four rewrites costs you four times. Cheap tokens make bad habits feel free. In December they won't be.

Host:Back to the teardown. What's the bit that doesn't hold up?

Expert:The idea that the model is the thing producing reliability. It isn't. Across their internal agent runs, an agent being the model working through multi-step tasks on its own, success without human input dropped sharply as tasks got more complex. The reliability comes from scoping and review. Belfield says outright they've seen no measurable acceleration of AI research driven by AI itself.

Host:Hang on, say that again.

Expert:No measurable acceleration. Their capability index, a score they built across a lot of models and benchmarks, grows at a steady pace. Argon sits slightly above trend, and they credit more compute and organisational investment. Money and people, basically.

Host:Money and people. The two oldest productivity tricks.

Expert:Before prompt engineering was cool.

Host:Uncomfortable question. Isn't this Google lowballing itself so regulators relax?

Expert:Could be motive in there, I can't see inside their heads. They're internal figures, not an audit. But Bloomberg reported some Google employees saying Argon scores well on benchmarks and does less well on real work, front-end design for one. Google called that inaccurate.

Host:So staff and company disagree.

Expert:And that disagreement proves my point. A benchmark is a task somebody wrote a check for. Front-end design, "make it look good", nobody wrote the check. The model's great until the finish line goes blurry.

Host:Which brings us to the rule you keep waving around.

Expert:Write the check before you write the prompt. If the check fits in one sentence, delegate. If it needs a paragraph, split the task. If you can't write it at all, the model is a sparring partner, not a worker.

Host:Give me a one-sentence check.

Expert:"Every figure in the summary matches the source table." Or "The email is under a hundred and fifty words and names the deadline." You can check those in seconds.

Host:And the paragraph one?

Expert:"A good quarterly memo is accurate, persuasive, on-brand, short, and flags risks." That's five jobs in a trench coat.

Host:Five jobs in a trench coat, trying to get into the cinema at the child price.

Expert:And the model will do two of them well and quietly fumble the others. Split it.

Host:Here's where I push back. Your rule sounds like it shoves all the interesting work into "sparring partner." That feels like a cop-out. Models write decent strategy drafts now.

Expert:Drafts, sure. But you're the check. If you can't say what done looks like, the model can't either, it just sounds confident.

Host:People can't say what done looks like for half their own strategy decks, and they still ship them.

Expert:Yes, and those decks are bad.

Host:Some are bad. Some are good because someone argued with a draft. I'm not convinced the line is as clean as you think.

Expert:It's not clean. It's useful. Different thing.

Host:We'll leave that bleeding. Next piece of the artefact: how Google tells people to prompt Argon. Vendor guidance about its own product, so salt.

Expert:Salt, but it's unusually specific. Tip one: before starting, have the model confirm it has the tools and docs and understands your intent. In their coding environment, Antigravity, there's a command called "grill-me" where the model interviews you with clarifying questions before writing a line.

Host:Grill-me. Someone at Google enjoyed naming that.

Expert:Somebody got a promotion. But it works because ambiguity in the brief turns into errors in the output. A minute of questions catches the bad assumption you'd otherwise find on page four.

Host:And they say let it run, but pause before irreversible steps.

Expert:Deleting things, sending things, paying for things. The chef lets the robot chop. Not plate the wedding cake unsupervised.

Host:There's a retrospective trick too.

Expert:My favourite. At the end of a session you ask the model to look back at where things stalled and propose updates to your AGENTS file, a standing instruction document the agent reads every time. Translate that to normal life: after a bad run, edit your saved instructions. People who do that get better every month. Everyone else starts from zero every Monday.

Host:Now the folklore. Tear down the bit everyone still does.

Expert:Wharton's Generative AI Labs, independent academics, tested it. Threatening the model or promising a tip: no meaningful effect on hard benchmarks.

Host:So I can stop telling my laptop I'll unplug its family.

Expert:Please do. It's not scared. It's embarrassed for you.

Host:And "think step by step"? Chain-of-thought, where you ask the model to show its reasoning?

Expert:Modest gains on older non-reasoning models, with answers getting more erratic. On reasoning models, the ones that already think before answering, marginal gains and a lot more waiting. You're asking a chess player to please consider his moves.

Host:What actually rattled you in that research?

Expert:The swing. Small wording changes moved individual answers by up to about thirty-six points on one test. So when someone tweaks a prompt, tries it once and declares victory...

Host:...they've basically flipped a coin and called it a methodology.

Expert:Exactly. You need a little test set. Twenty real past inputs, old prompt versus new, before you pick a winner.

Host:Honest moment. A lot of this "humans review everything" turns reviewers into the bottleneck. That lands a bit heavy for junior people whose job used to be writing the code.

Expert:Yeah. It lands heavy for me too. Reviewing well is a skill nobody trained them for, and it's suddenly the whole job. Teams should teach it on purpose.

Host:Okay. Practical stuff that's not in the code world. My memo has no compiler.

Expert:Right, code comes with tests, a forecast doesn't. Checking costs you more, so the check-first rule matters more for you, not less. Two cheap moves. First, show, don't describe. For tagging or sorting, a handful of labelled examples, shuffled so the model doesn't just copy the last one it saw. That's called few-shot prompting, teaching by example.

Host:And second?

Expert:Static stuff at the top. Style guide, policy, examples first, the changing question last. Argon caches shared opening text, meaning it remembers it and charges you far less for repeats. One independent guide warns it's not automatic, you need a cache hit, but the order is what makes it possible.

Host:Any company that's actually picked a measurable target?

Expert:Asana, per OpenAI, who sell the models involved, so treat it as vendor material and cross-check. They say Asana got its browser agent running about seventy-six times cheaper and faster by having the model run the experiments. The human picked the target and decided what counted as better.

Host:The human tasted the plate.

Expert:Always the plate.

Host:Give me one thing to do tomorrow. Just one.

Expert:Take the AI task you repeat most and write its check in one sentence, then paste that sentence into the prompt and tell the model to grade itself against it before handing anything over. If you can't write the sentence, stop delegating that task and start arguing with it instead.

Host:And stop threatening the laptop.

Expert:Especially that. It's watching you at the pass.

Host:Drawn from The Decoder, Alphaxiv and Alphasignal, links in the show notes. We'll stop there. The whole AI track, in order, is waiting at mba-training.com.

Read and go deeper