Cloudflare Flagship | Build or Be Replaced

Today: Cloudflare Flagship | That Methyl Methacrylate Tank | A few interesting modern pixel fonts Episode date: 2026-05-27.

Download MP3 →

Transcript

JOSH: It's Wednesday, May 27. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: Today is about the systems behind the systems. Communities, pipelines, local AI, and the quiet little guardrails that keep your automation from lighting the curtains on fire. JOSH: Stick around — Erik's got an AI pro tip at the end about making agents show their work before they touch production. [pause] JOSH: First headline. Cloudflare is pushing Discord as the front door for its Workers community. Why does that matter? ERIK: Because developer platforms live or die by feedback speed. Docs are nice. GitHub issues are fine. But Discord tells you where people are confused today, not six weeks from now in a roadmap meeting. JOSH: Second one. A Hacker News thread about outsourcing plus local AI becoming cheaper than frontier labs. That sounds like a fight. ERIK: It is. The cost curve is bending hard. If you can run a decent local model, give it tools, and route the weird stuff to a frontier model, you don't need every token to be premium-grade gold dust. JOSH: Third. Somebody built a Git-tracked book production pipeline. That feels very Erik-coded. ERIK: Duuude, yes. Books are software now. Manuscript, review, edits, covers, exports, publishing metadata. Put it in Git, wire in agents, make every change traceable. That's not cute. That's how you ship without losing your mind. [pause] JOSH: Let's start with Cloudflare. Discord as developer infrastructure. Isn't that just a chat room? [beat] ERIK: That's the mistake. People hear Discord and think gamer chat with too many notifications. But for a platform like Cloudflare Workers, it's closer to live telemetry from the developer brain. JOSH: Live telemetry from the developer brain is slightly terrifying. ERIK: Accurate though. Think about it. A developer gets stuck deploying a Worker. They don't file a clean bug report. They say, "Why does this binding fail locally but work in prod?" That sentence is worth money. JOSH: Because it tells Cloudflare where the friction is? ERIK: Exactly. It tells them the docs missed something, the CLI message is bad, or the product model isn't obvious. That's gold if you catch it while the person is still building. JOSH: How does that compare to what you're doing with ScanBrief? ERIK: Same pattern, different feed. ScanBrief scored 217 items across 54 sources today. That's not me reading 54 feeds with coffee like some Victorian newspaper guy. It's a scoring system. It pulls the signals, ranks them, and tells me where attention should go. JOSH: So Cloudflare is doing that with humans. ERIK: Yep. Their Discord is a human signal bus. Mine is NATS and agents and feeds. Same idea. Get events into a place where something can react. JOSH: And the reaction matters more than the collection. ERIK: Collection is step one. If you collect a thousand signals and nothing acts on them, congratulations, you built a landfill. The value is routing. [beat] ERIK: A developer asks a weird Workers question. That can become a doc fix, a CLI warning, a product issue, or a sample repo. In my world, PrimeBus sees an error event, tags it, routes it to an agent, and sometimes Gandalf reviews the fix before it ever gets near prod. JOSH: Gandalf is your reviewer agent? ERIK: Yeah. Gandalf's job is not to be impressed. Gandalf blocks bad ideas. Overnight, 2 code changes were automatically reviewed by Gandalf and merged to production. That's the part people like. But the better number is the block number. JOSH: Wait, really? ERIK: PrimeBus auto-merger has run 3804 attempts since April 17. 950 merged, 2842 blocked by Gandalf, 12 escalated to me. That's the story. The system says no way more often than it says yes. That's how you sleep. JOSH: Most people would market the merge number. ERIK: Most people market the shiny part. I care about the brakes. Anyone can bolt Claude onto a Git repo and say "agentic." Then it commits nonsense because a test passed by accident. Cool, you automated bad judgment. JOSH: That's a rough product name. ERIK: Automated Bad Judgment dot ai. Probably funded by Friday. [beat] JOSH: So when a company moves developer support into a live community, what's the real win? ERIK: Speed. You shorten the loop between pain and product change. But you need structure. If Discord is just a pile of messages, it becomes noise. You need tags, moderators, summary agents, issue creation, weekly patterns. Same as infrastructure alerts. JOSH: Alert fatigue, but for product teams. ERIK: Exactly. Have you implemented runbooks today? Same question applies. If a hundred developers ask the same thing, don't admire the community engagement. Fix the thing they keep tripping over. [pause] JOSH: The second story is local AI plus outsourcing becoming cheaper than frontier labs. Give me the plain-English version. ERIK: Frontier models are amazing. Claude, GPT, Gemini, all of it. But you don't need the most expensive brain for every task. You need the right brain for the job. JOSH: Like what? ERIK: Classification, formatting, scraping cleanup, simple code transforms, log summaries. Local models can handle a lot of that now. My Hermes box is a local agentic backend on a Mac M3 running qwen3-coder. It gives me about 70 tokens a second. That's usable. JOSH: That surprises me. ERIK: It surprised me too, and I build this stuff every day. The trick is not pretending the local model is magic. Give it narrow jobs. Give it tools. Give it tests. Let it fail cheap. JOSH: Where does outsourcing fit? ERIK: Some work is still better with humans. Data labeling, design review, QA passes, weird judgment calls, sales research. But pair a lower-cost human workflow with local AI and you can beat a pure frontier-model pipeline on cost. JOSH: Is that bad news for the big AI labs? ERIK: Not really. It's bad news for lazy architecture. Frontier labs still win on hard reasoning, long context, deep coding, weird edge cases. But if your whole system sends every lowercase task to a premium model, you're burning money because the architecture is simple. [beat] JOSH: What's the better pattern? ERIK: Router first. Local model first for low-risk tasks. Frontier model for high-risk tasks. HumanRail-style human review when confidence is low or the blast radius is high. Then log all of it. JOSH: You said HumanRail-style. Is that the idea where agents can hand work to a person? ERIK: Right. When the model isn't confident, route to a human. Don't make the agent fake certainty. Fake certainty is expensive. JOSH: How does that show up in your actual systems? ERIK: PrimeBus processed 2732 automation events across 5 projects today. Not all those events deserve the same model. Some are boring telemetry. Some are code changes. Some are production signals. Treating those equally would be dumb. JOSH: So you classify before spending. ERIK: Always. Same way a network engineer doesn't send every packet through the most expensive inspection path unless they hate money and latency. JOSH: That's a very network-engineer sentence. ERIK: It's true though. I spent years with NSO and network automation. You learn fast that control planes matter. AI systems are control planes now. If your routing logic is bad, your model choice won't save you. [beat] JOSH: Where do people get this wrong? ERIK: They start with the model. "Should I use Claude or GPT?" Wrong first question. Ask what the task is, what failure costs, what evidence exists, and who reviews the output. JOSH: Give me an example. ERIK: The PAS website-pipeline can build and maintain agency websites. If it's changing button spacing on a draft site, local model or cheaper model is fine. If it's changing pricing copy on a live customer page, I want stronger review and probably a human approval gate. JOSH: Same system, different risk. ERIK: That's it. People keep looking for one model to rule everything. That's not engineering. That's shopping. JOSH: Harsh. ERIK: Accurate. Builders need systems. Consumers need subscriptions. [pause] JOSH: The Git-tracked book production pipeline. Why did that jump out to you? ERIK: Because content work has the same problem software had before version control. People pass around final-final-really-final documents, and then they wonder why publishing feels haunted. JOSH: Haunted publishing does sound bad. ERIK: It's terrible. A book has chapters, edits, review comments, cover files, metadata, exports, landing pages, pricing, launch assets. That's a build pipeline. JOSH: And Git makes the history visible. ERIK: More than visible. It makes it recoverable. You can branch a chapter. You can run checks. You can diff edits. You can have agents review for tone, continuity, missing citations, layout issues. Then you know what changed and why. JOSH: You used AI to write your own book fast, right? ERIK: Yeah, but the speed isn't the point. The point is control. If you're using AI for long-form work and you don't have versioning, you're gambling. One bad prompt can erase a thread of thought. One sloppy regeneration can flatten your voice. JOSH: That's a real risk for this show too. ERIK: Absolutely. Build or Be Replaced is a daily AI and automation build log, but the process matters. Episode 31 today. The system needs voice rules, source signals, stats discipline, promo rotation, sponsor copy, all of it. If that isn't structured, the output turns into soup. [beat] JOSH: Soup is bad. ERIK: Soup is fine for lunch. Bad for production media. JOSH: What would you put in a serious content pipeline? ERIK: First, sources in a folder or database. Not vibes. Actual source text. Second, prompts in Git. Third, generated drafts stored with metadata: model, date, inputs, version. Fourth, checks. Did it use banned words? Did it cite only allowed stats? Did it follow the format? Fifth, review gates before publish. JOSH: That sounds like software CI. ERIK: It is software CI. Content is code with more feelings. JOSH: That's going on a mug. ERIK: It should go in a repo first. [beat] JOSH: Where do agents help the most there? ERIK: Repetition. Agents are great at boring passes. Check every line starts with the right speaker. Check sponsor read is exact. Check Wednesday promo is the Wednesday promo. Check no bracket markers are inside dialogue. That's not creative work. That's guardrail work. JOSH: And the creative part? ERIK: Humans still set taste. Agents can draft, compare, critique, and fix. But somebody has to know what good sounds like. Otherwise you get a perfectly formatted pile of nothing. JOSH: That feels like the theme today. Systems don't remove judgment. ERIK: Right. They move judgment to better places. I don't want to personally inspect every telemetry event. I do want to decide what gets blocked, what gets merged, and what wakes me up. [pause] JOSH: Quick detour. The Launch HN item for Windows desktop automation at scale. Worth watching? ERIK: Yes. Desktop automation refuses to die because businesses still run weird Windows apps that don't have APIs. Selenium helped web automation. RPA helped desktop automation. AI might make the brittle parts less painful, but screenshots and clicks are still a messy interface. JOSH: So you're not dismissing it. ERIK: No. If the business process lives inside a Windows app, that's where the automation has to go. I'd rather have an API. But I'd also rather have a working system than a purity argument. JOSH: That's very practical. ERIK: Practical pays invoices. [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: Make your agent write a pre-flight report before it changes anything. JOSH: What goes in it? ERIK: Four fields. Intent, files or systems touched, failure risk, and rollback plan. Keep it short. Force the model to say what it thinks it's about to do. JOSH: Why does that help? ERIK: Because agents make fewer dumb moves when they have to declare the move first. It also gives your reviewer, human or AI, something concrete to check. If the intent says "update CSS" and the touched files include billing code, stop the run. JOSH: Simple guardrail. ERIK: Very simple. Add it before tool calls, before deploys, before database writes. Then log the pre-flight next to the result. After a week, you'll see patterns. Which tasks fail. Which prompts are vague. Which agent keeps reaching into places it shouldn't. JOSH: That's usable today. ERIK: Yep. Don't start by making the agent smarter. Start by making it accountable. 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] 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.