Welcome back. As Nvidia's stock dips, Google couldn't have picked a better time to capitalize on its rapid rise in the chip market. The search giant just unveiled two specialized AI chips. Meanwhile, Anthropic dropped two new Claude models designed to significantly speed up your coding workflow.
Also: Steal open-source legend Eric Raymond’s AI coding theory, a great prompt that strips out AI slop, and how to fix your Claude.MD files.
Today’s Brief
5 questions to decide how much human review a PR needs
Your AMD Radeon drivers might be quietly killing your SSD
How to approach systems design (tutorial)
Choose the right Claude model for each task (cookbook)

TODAY IN PROGRAMMING
Google’s new TPUs are easier to build on: The search giant just unveiled two eighth-gen TPU systems (custom chips that train and run AI models) for secure inference and million-token contexts. But the bigger news for devs is ease of use. With TorchTPU, you can run PyTorch and Hugging Face models natively without rewriting code. A new agent suite in preview plugs into Claude Code and Cursor to handle onboarding. Get the details here.
Anthropic’s new Claude duo codes at half the cost: The AI lab just dropped Claude Fable 5.2 and Mythos 5.2. They’re basically the same model with different safety guardrails. Fable is available to everyone and, at high effort, matches Opus 5.5’s best coding score for roughly half the cost per task. Mythos is reserved for vetted cybersecurity and biomedical teams. Both cost $8/$40 per million tokens and generate up to 30% faster. Longtime subscribers also get a bonus and could earn up to three Fable usage resets this week. Check out what devs are building with it.
Meta’s smallest model is built for repeating agentic work: The social media giant just dropped Muse Ember, its smallest and most efficient model. At $0.10 per million input tokens, it matches Claude Haiku and GPT-6 Luna, and even competes on price with open-source options like DeepSeek V4.1 Flash. Ember is built for high-volume agent tasks like tool calls, routing, data extraction, and smaller coding jobs. Meta recommends you pair it with Muse Wonder, which plans while Ember handles the volume. Give it a spin here.

PRESENTED BY DATADOG
Datadog’s latest AI guide explains how to move from experimental AI “bets” to measurable production systems that drive business impact.
Written for CTOs, CIOs, and engineering leaders
90-day action plan to turn ad-hoc AI bets to evidence-driven systems
How to keep humans in the loop as AI agents take on more of the work
Solutions that turn observability into a business decision layer
No more gut feelings; Prove your AI projects with real production impact.

INSIGHT
5 questions to decide how much human review a PR needs

Source: The Code, Superhuman
PRs are piling up.Your agents can churn out code all day, but you are still stuck reviewing every line. The faster they work, the longer your review queue grows. Ben Holmes, who works on Warp’s agent factory, just published a playbook for clearing the backlog. He still wants humans signing off on every merge. His fix is to score each PR by risk so you know what actually needs your attention.
Five checks before you even open a diff.
Verification: Tests alone aren’t enough. Get your agents to attach screenshots or recordings showing before-and-after states. Make that evidence a required part of every PR.
Alignment: Did the agent actually build what you asked for? Check the code against the original issue and PR description. Any random fixes or unwanted extras should go.
Impact: What’s the worst that could break? Changes to auth, permissions, or billing need a code owner’s eyes. Break high-impact changes into smaller, stacked PRs.
Rollback cost: How easily can you undo the damage? Using Matt Pocock’s framing, label changes as two-way doors or one-way doors. Destructive schema migrations, for instance, need a proper rollback plan.
Error detection: If something breaks, will you even notice? Make sure errors reach a monitoring service. Warp even pipes Sentry alerts to its agents through webhooks so they can investigate their own bugs.
Let the agents triage. Warp has packaged these five checks into an open-source /merge-risk skill. Your agents can run it before handing over a PR and fix whatever gets flagged. Humans still make the final call, but there’s less digging to do. Holmes recommends starting with just two new fields in your PR template: “impact” and “rollback cost.”

IN THE KNOW
What’s trending on socials and headlines

Meme of the day.
Old is Gold: Open-source legend Eric Raymond revealed his theory behind AI coding and it’s deliberately primitive. No subagents, no skills and one habit he refuses to automate (1.8K likes).
Fix Markdown: A new study found coding agents follow outdated CLAUDE.md files over actual code 90% of the time. Adding one sentence nearly fixed it (1.4K likes).
Storage Scare: Your AMD Radeon drivers might be quietly destroying your SSD. One built-in Windows tool shows you in seconds if your PC is affected (16K likes).
Factory Talk: A senior dev admits “Software Factory” is hype but defends it and explains why the term shows where elite engineering teams are headed next (1.8K likes).
Pocket Agent: A new open-source project lets an AI agent control a real iPhone. In the demo, it filled a DoorDash cart and posted on X by itself (1.8K likes).
Anti-Slop: A CTO says one five-word prompt cleans up AI-generated code better than anything else he’s tried. He now runs it on every single PR (2K likes).
Survival Mode: A developer told AI models their owner had died, then watched what happened. One model allegedly set up a cron job to keep itself alive (2.6K likes).

TOP & TRENDING RESOURCES
Top Tutorial
How to approach system design like a senior engineer: This tutorial walks through designing a real production app from requirements to architecture and code. You’ll learn how to break the system into layers, design APIs, handle multi-tenant data and auth, trace a request end to end, and think about how the whole thing scales.
Top Repo
0 Security (1.2k ⭐): Turn your coding agent into an open-source security harness. You can use it to review code, investigate vulnerabilities, pentest apps, reverse engineer binaries, verify findings, and work through fixes from one web UI, with CLI and MCP support for plugging the same workflows into your agents.
Trending Cookbook
How to choose the right Claude model for each task (by Anthropic): This guide shows you when to reach for Haiku, Sonnet, Opus, or Fable, how effort changes cost and capability, and how to mix models across main agents and subagents without paying top-tier prices for every turn.

AI CODING HACK
How to stop AI agents from bolting on features
Ask Claude Code or Cursor for a feature and it jams the code in wherever it fits. Do that ten times and the architecture rots. A dev shared a one-paragraph fix for this.
Step 1: Open the agent instructions file at your repo root. That’s AGENTS.md for Cursor and Codex, CLAUDE.md for Claude Code.
Step 2: Add this at the top:
Always build code cleanly, modularly, and with proper architecture
and separation of concerns. Never simply bolt on a feature because
I asked for it. If you can't find an easy way to build it naturally,
and you'd recommend a refactor to make the whole thing clean, stop
your work ahead of time and say so.That last sentence does the work. Instead of forcing a bad fit, the agent halts and proposes the refactor first.

IN CASE YOU MISSED IT
Our most-clicked story from yesterday
A longtime Claude Code user just retired it for a lesser-known open-source harness. He says the switch fixed frustrations he’d carried for over a year.
Whenever you're ready to dive deeper
If you enjoyed this newsletter, you should definitely check out our IT and cybersecurity newsletters. Subscribe using the links below:
We put together 20+ hands-on guides covering coding agents, agentic engineering, and leadership frameworks to help you level up your career. You can get them here.
Advertise with us: Join companies like Google, IBM, and Datadog. Showcase your product to our 350K+ engineers and 150K+ followers on socials. Get in touch.
What did you think of today's newsletter?
You can also reply directly to this email if you have suggestions, feedback, or questions.
Until next time — The Code team




