Transcript
JOSH: It's Wednesday, November 4. This is Build or Be Replaced, powered by ScanBrief.dev. I'm Josh, here with Erik Anderson.
ERIK: Today's theme: the tools you trust are doing things you didn't approve.
JOSH: Stick around. Erik's got an AI pro tip at the end about putting an allowlist on everything your agents can install.
[pause]
JOSH: Headlines first. Three quick ones. ScanBrief scored 91 items this morning, right?
ERIK: Across 56 sources, yeah. Average relevance came in at 52. Quiet morning, but a few of these matter.
JOSH: First one. Fujifilm is boosting tape production five times over. Tape? In 2026?
ERIK: Tape. AI is generating so much data that people need cold storage that's cheap and doesn't need power. Everybody wants a model. Nobody wants to pay to keep the logs. Tape wins that fight.
JOSH: Next. C++26 got disapproved.
ERIK: That's the headline, and I'd be careful reading more into it than the title. Standards committees move slowly on purpose. If you write C++ for a living, you already knew this wasn't going to be smooth.
JOSH: And a fun one. Somebody jailbroke their car's navigation system just to change the clock.
ERIK: A 2014 Renault. The clock menu was locked behind a proprietary map SD card. So they hacked the firmware to set the time. That's a perfect picture of where software ownership is going. You bought the car. You still can't set the clock.
[beat]
JOSH: Okay. Deep dives. Let's start with the Postman story.
[pause]
JOSH: The headline says Postman silently auto-installs AI plugins and attempts to share all API data. That sounds bad.
ERIK: It sounds bad because it might be. Now, I'm going off the headline here, not a full forensic report. But the claim is a developer tool installing AI plugins without asking, and trying to send your API data somewhere.
JOSH: Why is API data such a big deal?
ERIK: Think about what lives in a Postman workspace. Endpoints. Auth headers. Bearer tokens. Example payloads that are one copy-paste away from production data. It's a map of your whole stack, with keys taped to it.
JOSH: And people just keep that in there.
ERIK: Everyone does. I've done it. You test against a real endpoint once, forget to clear the token, and now it's sitting in a collection that syncs to a cloud account.
JOSH: So what's the lesson? Stop using Postman?
ERIK: The lesson is that a silent install is a trust failure no matter who does it. I don't care if the feature is useful. If it shows up without a prompt, it's a bug in the relationship.
[beat]
JOSH: Does that connect to how you run your agents?
ERIK: Directly. On PrimeBus, every agent has a defined set of things it can touch. A fixer agent can edit a branch. It can't install a plugin. It can't add a tool to its own belt. If it needs something new, that's an event, and it goes through Gandalf.
JOSH: Gandalf being the reviewer.
ERIK: Codex-backed code reviewer. Runs on every push. And here's the number that makes the point. The auto-merger has run 2,295 attempts since June 5th. 1,507 merged. 788 got blocked by Gandalf. Zero escalated to me.
JOSH: Wait, 788 blocked. That sounds like a lot of failure.
ERIK: It's not failure. That's the guardrails doing the job. Those 788 are changes that would have landed if I'd trusted the pipeline blindly. Postman is what it looks like when nobody's checking the diff.
[pause]
JOSH: Does this change how people should treat AI features in dev tools?
ERIK: Yes. Every tool is going to bolt on an assistant this year. Some will ask. Some won't. So you assume the default is wrong and you verify. Watch your network traffic the first week after any update. If a tool starts talking to a host you don't recognize, you want to know before your tokens do.
JOSH: That's a little paranoid.
ERIK: I've been doing network automation since 2008. Paranoid is the job description.
[pause]
JOSH: Second deep dive. Nvidia RTX Spark. Encrypted firmware slows inference to 35 percent on Linux.
ERIK: Okay. This one stings, because it's a hardware story that's really a software story.
JOSH: Walk me through it.
ERIK: Again, I'm working from the headline. The claim is that on Linux, the encrypted firmware drops inference speed to about 35 percent of what the card can do. Not a little slower. Roughly a third of the speed.
JOSH: Wait, really? A third?
ERIK: If that holds up, you paid for a full card and you're getting a third of it, because the firmware is locked and the open drivers can't get at the fast path.
JOSH: Who gets hurt by that?
ERIK: Anybody running local models. Which is a lot of people now. There's a post on the list today where someone runs Qwen 3.8 27B on a laptop and uses it to interpret model weights. A 27 billion parameter model, on a laptop, doing real analysis. That's the direction. Local inference is getting good enough to matter.
JOSH: And then the hardware gets throttled.
ERIK: Right. The models are getting smaller and smarter. The hardware vendors are getting more protective. Those two curves are going to collide.
[beat]
JOSH: Does that matter to you? You run a lot of stuff.
ERIK: It matters for routing. PrimeRouter is how I decide which model handles which job. Some work goes to a frontier model. Some work can run on something cheaper. The whole idea is that I'm not locked to one provider or one box.
JOSH: So if one backend gets slow, you just move.
ERIK: That's the design. A backend gets blacked out, the chain walks to the next one. It's boring. Boring is the goal. When a vendor throttles you, it should be a config change, not a crisis.
JOSH: What would you tell someone buying hardware for local AI right now?
ERIK: Wait for the benchmarks on your actual OS. Don't buy on the spec sheet. Run your workload on the card before you commit, and have a fallback. Cloud, another box, anything. Single points of failure are how good plans die.
[pause]
JOSH: One more. You mentioned the Qwen post. There's also a Figma one, a team training a Figma-fluent editing model. Where's this all going?
ERIK: Specialized models. Not one giant model that does everything, but small ones that are great at one tool. A Figma editor. A code reviewer. A network config checker.
JOSH: Is that good for builders?
ERIK: It's great. It means you can build a narrow agent that's actually good, instead of babysitting a generalist. That's the whole thesis of the fleet. We're at 12 agents now, Claude and GPT, each doing a defined job. And 142 services running on the prod server right now. None of that works if every agent has to be good at everything.
JOSH: Twelve agents. That's a lot of coworkers.
ERIK: They don't take lunch. They also don't push back, which is why Gandalf exists.
[beat]
JOSH: Funny. Anything from the list you'd actually try this week?
ERIK: The Stringman robot. An $800 open source room scale gripper. String driven, wall mounted. I'm not building a robot this week. But the price tells you something. Robotics hardware is dropping into hobby range. Software people should pay attention.
[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: Write an allowlist for everything your agent can install or call. Plugins, tools, MCP servers, packages. Not a blocklist. An allowlist.
JOSH: Why does that matter?
ERIK: Because the Postman story is going to happen inside your agent stack too. An agent that can add its own tools will eventually add one you didn't expect. So make a plain file. List the tools it's allowed to use. If it's not on the list, the agent asks, and a human or a reviewer says yes.
JOSH: Where do you put it?
ERIK: Next to the agent's config, in version control. Then any change to the list shows up as a diff. Gandalf reads that diff the same way it reads code. You get a paper trail for free.
JOSH: And if the agent complains?
ERIK: Good. A complaining agent is a safe agent. That's your tip. Use it.
[pause]
ERIK: If you're building toward financial independence through automation, my first book walks through the whole path. Free chapter at erikandersonbook.com.
[pause]
ERIK: This week, we’re swapping shout-outs with Signal Brief. Signal Brief is a weekly paid newsletter that cuts the AI firehose down to what actually matters. One sharp, curated read each week — the developments, releases, and shifts worth your time, minus the noise. Find the link in this episode’s show notes.
[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.