Mon–Fri · 6 AM ET
← All Episodes
EP  • 00:08:13

RIP, Harvest | Build or Be Replaced

Today: RIP, Harvest | Writing as a thinking tool | Goldman Sachs is pulling Claude Code from its bankers and traders Episode date: 2026-11-09.

Download MP3 →

Transcript

JOSH: It's Monday, November 9. This is Build or Be Replaced, powered by ScanBrief.dev. I'm Josh, here with Erik Anderson.
ERIK: A bank pulls its AI tool, a model gets accused of going soft, and Microsoft starts bouncing your mail. Trust is the theme today.
JOSH: Stick around. Erik's got an AI pro tip at the end about catching a model getting worse before your users do.
[pause]
JOSH: Headlines. ScanBrief scored 82 items across 56 sources this morning. What jumped out?
ERIK: Plenty. Let's start quick.
JOSH: There's a project called Llama-modchip. A 284B DeepSeek running on 64GB of RAM, no GPU. Is that real?
ERIK: That's the headline claim, and I'd want to run it before I trust it. But the direction matters. Every month the floor for running a big model locally drops. If that holds up, a lot of "we need a GPU cluster" budgets get awkward.
[beat]
JOSH: Next one. Researchers say they can unlock any car from one brand, worldwide, through an unauthenticated API.
ERIK: Unauthenticated. On the telematics backend. That's not a clever exploit, that's a missing door. I spent years in network automation, and the pattern never changes. The mobile app gets all the security attention and the API behind it gets none.
[beat]
JOSH: And someone wrote that they're not convinced the AI bubble exists.
ERIK: The argument is that five trillion dollars of spending is still justifiable. Maybe. I don't trade on bubble talk. I look at what I ship every day, and that doesn't care what the stock market thinks.
[pause]
JOSH: Okay. Deep dives. Goldman Sachs is pulling Claude Code from its bankers and traders. That one's lighting up Hacker News.
ERIK: It is, and the headline is all we have. I haven't seen a memo, so I'm not going to invent their reasons. But I can tell you what it usually looks like when a regulated shop pulls a coding agent.
JOSH: What does it usually look like?
ERIK: Control. Not capability. A bank has to answer one question for an auditor: what did that tool touch, and who approved it? If the answer is "the agent had a shell and a lot of freedom," compliance says no. And compliance is right to say no.
JOSH: So it's not that the tool is bad.
ERIK: Probably not. It's that the tool was handed out like a laptop sticker. Here's the thing. Bankers and traders aren't engineers. Give a trader an agent with write access and you've got someone who can change things without understanding what they changed.
[beat]
JOSH: Wait, really? You think that's the whole story?
ERIK: I think it's the likely story. Wide access, thin guardrails, no audit trail. That combination gets shut down in every industry, not just banking.
JOSH: How does that compare to what you run?
ERIK: Opposite philosophy. PrimeBus runs my auto-merge pipeline, and the agents don't just get to ship. Since June fifth, the auto-merger has run 2,295 attempts. 1,507 merged. 788 got blocked by Gandalf, the review gate. Zero escalated to me.
JOSH: Seven hundred eighty-eight blocked. That sounds like a lot.
ERIK: That's the story. Those aren't failures. That's the guardrail doing its job. If I'd handed an agent raw access to prod, all 788 of those would've been a mess in production. Instead, they were a line in a log.
[beat]
JOSH: So what's the lesson for someone at a big company?
ERIK: Don't ban the agent. Build the gate. Every action goes through a bus, every change gets reviewed, everything's logged. Then when an auditor asks, you show them the log. A bank that pulls the tool without building the gate will be back in six months with the same problem and a worse vendor.
JOSH: And if they don't build it?
ERIK: Then their competitors who did are shipping faster, and the bank is holding a ban order. Build or be replaced, I guess.
[pause]
JOSH: Next. Somebody on Hacker News asks, "Is Opus 5.5 nerfed? Thinking patterns changed on November 3."
ERIK: And that post will get a thousand replies saying "yes, I noticed too." Let me be careful here. I can't tell you whether anything changed on the provider side. Nobody outside can, from vibes.
JOSH: But people feel it.
ERIK: They do. And that's the real problem. When your workflow depends on a model, a behavior change feels like a nerf even if it's just different. Shorter reasoning, different formatting, a new refusal. Your prompt that worked for two months suddenly doesn't.
[beat]
JOSH: Has that happened to you?
ERIK: A model changing behavior under me? Sure. That's why PrimeRouter exists. It sits between my services and the models, so no single project is hard-wired to one backend. If one starts acting different, I change a chain in one place instead of editing every project.
JOSH: So you can just swap it out.
ERIK: Carefully. Swapping a model is a change like any other. I test it first, I watch it, and I keep a way back. But yes, the point is that one model's mood swing is not an emergency.
JOSH: What would you tell someone who feels like their model got dumber?
ERIK: Prove it. Don't argue about it. Keep a set of prompts with known good answers, run them regularly, and compare. If the score drops, you have evidence. If it doesn't, the problem might be your prompt or your mood. I'll give you the exact version in the tip.
[pause]
JOSH: Third one hits email. Outlook.com is rejecting mail from domains without DMARC.
ERIK: This is the one I'd put on a sticky note. If you send email for a business and you have no DMARC record, Microsoft is now telling you no. Not spam folder. Rejected.
JOSH: Isn't that something people were warned about?
ERIK: For years. Google and Yahoo started pushing it, and now Outlook's following. If you've been ignoring it because mail "mostly works," mostly just ended.
[beat]
JOSH: Who gets hurt?
ERIK: Small businesses. The plumber with a website and a contact form that sends through some plugin. Their quote requests silently disappear and they have no idea. The customer thinks they were ignored. The business thinks nobody's calling.
JOSH: That's brutal.
ERIK: It's also fixable in an afternoon. You need SPF, you need DKIM, and you need a DMARC record that ties them together. Start with a monitoring policy so you can see what's sending as you, then tighten it.
JOSH: And you handle this on your own stuff?
ERIK: Every outbound message from my systems goes through one path. SES, with a deliverability layer on top that handles authentication and suppression. Nothing sends mail on its own. That's not an accident. One door means one place to check DMARC, and one place to fix it when a provider changes the rules.
JOSH: So when Outlook tightens up...
ERIK: I'm not scrambling. I check one path. If you've got five different tools each sending mail from your domain, you've got five problems and no map.
[beat]
JOSH: Practical step for somebody listening right now?
ERIK: Look up your own domain's DMARC record. Takes a minute. If it's empty, that's your homework today. Then send yourself a test to an Outlook address and see what happens.
[pause]
ERIK: This episode is sponsored by Prime Automation Solutions. If you're still doing it manually, we automate it. Also, special on a website — $250. primeautomationsolutions.com
[pause]
JOSH: Alright, what's the AI pro tip today?
ERIK: Build a canary set for your model. Ten to twenty prompts from your real work, the ones where you already know what a good answer looks like. Save the prompts, save the good outputs, and write down what you check for. Length, format, whether it follows the instruction, whether the code actually runs.
ERIK: Then run that set on a schedule, same settings every time, and log the results. When someone on Hacker News says the model got nerfed, you open your log. If your scores held steady, ignore the noise. If they dropped on a certain date, you've got a timestamp and evidence, and you can switch models without guessing.
ERIK: Run it again any time you change a prompt or a model version. It costs pennies and saves you a week of chasing a ghost. That's your tip. Use it.
[pause]
JOSH: That tip is straight out of The Autonomous Engineer, huh?
ERIK: That tip is straight out of The Autonomous Engineer — my book on building systems that run themselves. Grab it on Amazon.
[pause]
JOSH: One more thing — we started a Discord for builders. If you're shipping AI, automation, or anything that makes a human obsolete — come hang out. Link at buildorbereplaced.dev.
ERIK: Post what you built. We'll post what we're building. Real wins, real builds, no fluff.
[pause]
ERIK: Build or be replaced.
JOSH: If you want these signals in your inbox every morning, scanbrief.dev. See you tomorrow.