Build or Replaced
Today: Learning to code is still worthwhile | Resetting Xbox | How to sequence your own DNA at home Episode date: 2026-07-07.
Download MP3 →JOSH: It's Tuesday, July 7. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: Episode 60, 117 services running, and the theme today is simple: builders still win when the tools get cheaper. JOSH: Stick around — Erik's got an AI pro tip at the end about using small models before you burn money on big ones. [pause] JOSH: First headline. Hacker News is arguing that learning to code is still worthwhile. Erik, is that even a debate? ERIK: It shouldn't be. The people saying coding is dead are usually the people who never built anything without a tutorial. AI makes coding more valuable because now one good builder can command a whole fleet. JOSH: Next up, GLM 5.2 and the coming AI margin collapse. That sounds expensive for somebody. ERIK: Expensive for model companies, good for builders. If inference margins collapse, the cost of running agents drops, and systems like PrimeBus get cheaper to operate every month. JOSH: Third headline. OpenWrt One has an open-hardware router, WiFi 6, 2.5G WAN, M.2, and apparently a manufacturing defect causing compatibility issues. ERIK: That's the most networking sentence of the day. Great idea, real hardware, weird defect, somebody's weekend disappears. [pause] JOSH: Let's start with coding. The headline says learning to code is still worthwhile. A lot of people hear AI coding tools and think, okay, why bother? [beat] ERIK: Because the tool still needs a driver. Claude can write code. GPT can write code. Cursor can patch files. Codex can reason through a repo. But if you don't understand what good looks like, you're just accepting whatever comes back. JOSH: So the skill moves up a layer? ERIK: Exactly. Syntax matters less. System judgment matters more. You don't need to memorize every Python method anymore. Fine. But you better know when the model created a race condition, leaked a secret, broke idempotency, or made your automation retry until it burns the building down. JOSH: That's the part beginners don't see. ERIK: Right. They see the demo. Prompt in, app out. Looks cool. Then the app gets real traffic, or the database has dirty data, or the network call times out, and suddenly the magic chatbot is holding a chainsaw. JOSH: Wait, really? ERIK: Duuude, yes. The first version is never the system. The system is the retries, telemetry, dead-letter queue, rollback path, tests, approvals, and the boring stuff that saves you at 2 AM. JOSH: That's where your PrimeBus setup comes in. ERIK: Yep. PrimeBus processed 11 automation events across 1 project today. That's not a giant number, but that's the point. It sees the events. It routes the work. It lets agents act without me sitting there refreshing logs like a sad little dashboard goblin. JOSH: You said the thing. ERIK: Fine. One-time exception. [beat] ERIK: The real stat is the auto-merger. Since June 5, it's run 2295 attempts. 1507 merged. 788 blocked by Gandalf. Zero escalated to me. That's the story. Not that AI magically writes perfect code. It doesn't. The story is guardrails caught the stuff that shouldn't ship. JOSH: So learning to code now means learning how to supervise machines? ERIK: Supervise, constrain, and verify. That's the job. You tell the agent what done means. You give it tests. You make it prove the change. You keep humans in the loop where the blast radius is high. Then you let it move fast where the risk is low. JOSH: What would you tell someone starting today? ERIK: Build something ugly that works. Don't start with a course that teaches perfect abstractions for six months. Build a scraper. Build a webhook receiver. Build a Discord bot. Build a small NATS worker that listens for a message and does one useful thing. JOSH: Why NATS? ERIK: Because event-driven systems teach the right mental model. Input comes in. Worker reacts. Result goes out. Logs exist. Failures are visible. That's automation. That's how you stop thinking in scripts and start thinking in systems. JOSH: So AI doesn't replace the need to learn. It changes what learning means. ERIK: Exactly. Learning to code in 2026 means learning how software behaves when nobody is watching it. That's where the money is. That's where the jobs are. That's where the builders separate from the prompt tourists. [pause] JOSH: Okay, AI costs. GLM 5.2, margin collapse, inference getting cheaper. Why should a normal builder care? ERIK: Because cost controls architecture. When inference is expensive, you ration intelligence. You send the big model only the important stuff. When inference gets cheap, you start putting little brains everywhere. JOSH: Little brains everywhere sounds slightly alarming. ERIK: It should. But it's also useful. Think about ScanBrief. It scored 85 items across 54 sources today, with an average relevance score of 52.6. That workflow doesn't need one giant model staring at the internet like a philosopher. It needs a pipeline. JOSH: What does that pipeline look like? ERIK: Fetch, dedupe, score, summarize, rank, publish. Some of that can be deterministic code. Some can be embeddings. Some can be a small model. Some can be a bigger model only when the item actually matters. JOSH: So don't send everything to the most expensive model. ERIK: Correct. That's lazy architecture. If every task goes to the biggest model, you didn't design a system. You bought a very expensive hammer. [beat] JOSH: Where does GLM 5.2 fit into that? ERIK: The signal is competition. More capable models, cheaper inference, more providers fighting for usage. Margins come down. API pricing gets compressed. Open weights keep pressure on closed systems. Builders get more choices. JOSH: Does that hurt OpenAI, Anthropic, Google? ERIK: It hurts the idea that model access alone is the business. If your whole product is "we call an API and add a nice button," you're in trouble. The durable value is workflow, data, trust, distribution, and integration. JOSH: That's a very SaaS answer. ERIK: It's the correct answer. The model is becoming an ingredient. Still important. Still powerful. But an ingredient. The product is the system around it. JOSH: How do you think about model choice in your own stuff? ERIK: I don't marry models. I route work. Claude is great for code and reasoning. GPT is strong in agent workflows and structured outputs. Small models are good for cheap classification, extraction, local tasks, and privacy-sensitive work. The system decides based on cost, latency, and risk. JOSH: That's more like network routing than app development. ERIK: Exactly. That's why network engineers should be eating right now. We already think in paths, queues, policies, failure domains, retries, and observability. AI agents are just noisy services with opinions. JOSH: That's a bumper sticker. ERIK: A depressing one, but accurate. [beat] JOSH: The list also had small AI models gaining traction in places with unreliable networks. ERIK: That's one of the better signals today. Not every useful AI system needs a data center round trip. If you're in a factory, a field truck, a clinic, a ship, a remote school, or a sketchy LTE zone, local models matter. JOSH: Smaller means weaker though, right? ERIK: For general reasoning, usually. For narrow tasks, not always. If the job is classify a ticket, extract fields from a form, summarize a known format, detect a bad log line, or pick the next runbook step, a small model can be plenty. JOSH: And cheaper. ERIK: Cheaper, faster, private, and less fragile. That's the part people miss. Cloud AI is great until DNS breaks, your vendor rate-limits you, or the budget owner sees the bill and develops a personality. JOSH: How would you use that in infrastructure? ERIK: Put small models near the work. A LAN dashboard like PrimeDash shouldn't need a frontier model to notice a service is down. A NOC tool shouldn't need a giant model to map "BGP neighbor stuck idle" to the first three checks in a runbook. Save the expensive model for the hard part. JOSH: What's the hard part? ERIK: Ambiguity. Novel failures. Code generation. Cross-system reasoning. Anything with a high cost of being wrong. That's where you escalate. JOSH: That sounds like HumanRail too. ERIK: Exactly. HumanRail is built around that idea. If the agent isn't confident, route to a human. AI doesn't need to pretend. It needs a clean path to say, "this is above my authority." JOSH: More systems should do that. ERIK: Most systems should do that. The macho version of automation is "no humans ever." That's nonsense. The real version is "no humans for routine work, right humans for risky work, full audit trail for everything." [pause] JOSH: Let's switch to hardware. OpenWrt One. Open hardware router, modern specs, but there's a manufacturing defect causing compatibility issues. Why did that make your list? ERIK: Because it's the builder story in one device. Open hardware is good. Open firmware is good. OpenWrt is important. But hardware is unforgiving. Software can be patched while you drink coffee. A board-level problem can turn into returns, rework, forum threads, and a lot of people saying "works on mine." JOSH: Networking people felt that. ERIK: Deeply. Routers are supposed to be boring. That's the compliment. If your router is exciting, something has gone wrong. JOSH: What do you like about the device? ERIK: 2.5G WAN, WiFi 6, dual-band, M.2, OpenWrt from the start. That's a real lab box. That's the kind of thing I want in front of builders because it teaches networking at the edge. JOSH: Why does open router hardware matter in an AI-heavy episode? ERIK: Because AI systems still hit the network. Agents call APIs. Workers pull containers. Telemetry ships events. Webhooks fire. If the network is trash, your automation is trash with better branding. JOSH: So the physical layer still gets a vote. ERIK: Always. I don't care how smart the agent is. If DNS is broken, it's sitting there staring at a timeout like everybody else. [beat] JOSH: How would you use something like OpenWrt One in a lab? ERIK: Segmented lab networks. Test WAN failover. VPN experiments. Local DNS. Firewall policy. Maybe a small telemetry collector. You can build a realistic edge environment without begging corporate for a change window. JOSH: That sounds useful for people learning automation too. ERIK: Very useful. Build a mini network. Break it on purpose. Have Terraform or Ansible push config. Use Selenium to test the web UI if you have to. Use NATS to emit events when state changes. Then make an agent explain what happened. JOSH: That's a lot more practical than watching another video. ERIK: Videos are fine. Building is better. You don't learn routing by nodding at a diagram. You learn it when you fat-finger a VLAN and have to walk across the room because you locked yourself out. JOSH: Pain-driven education. ERIK: Cheap pain. That's the trick. Lab pain is good. Production pain is expensive. JOSH: What about the defect? Does that make you avoid it? ERIK: Not automatically. I want transparency. Tell people exactly what failed, which batches are affected, what the workaround is, and what the replacement path looks like. Open hardware communities can handle bad news. They hate vague news. JOSH: That's fair. ERIK: Same rule as automation. Fail visibly. Fail with logs. Fail with a recovery path. Don't make people reverse-engineer your mistake from a forum post written at 1:17 AM. [pause] JOSH: One more thread before the sponsor. OfficeCLI showed up too, an office suite for AI agents to read and edit Microsoft Office files. Why does that matter? ERIK: Because business still runs on docs, spreadsheets, and slides. Engineers pretend everything is JSON and YAML. Then finance sends an Excel file with merged cells, hidden tabs, and a macro named FinalFinalRealOne. JOSH: That's too real. ERIK: Agents need to work where the messy work lives. If an AI agent can safely read a Word doc, update a spreadsheet, generate a proposal, and preserve formatting, that's useful. Not flashy. Useful. JOSH: Is that something you'd connect to ScanBrief or Build or Be Replaced? ERIK: For sure. ScanBrief is already a scored feed. Build or Be Replaced is a daily build log. The next layer is packaging output for humans in the formats they already use. Email, docs, PDFs, dashboards. Not every user wants an API endpoint. JOSH: Builders sometimes forget that. ERIK: All the time. The best automation often ends in something boring. A clean spreadsheet. A ticket with the right fields filled. A report sent before the meeting. Nobody claps. They just stop doing manual work. [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 model ladder. Don't start every task with the biggest model. Write down three tiers. Tier one is code: regex, parser, SQL, normal logic. Tier two is a small or cheap model for classification, extraction, and routing. Tier three is your best model for reasoning, code changes, and high-risk decisions. JOSH: How does someone apply that today? ERIK: Take one workflow. Maybe support tickets. First, use code to detect obvious fields: customer, service, timestamp, error code. Then use a small model to label the ticket: billing, outage, access, bug. Only send the weird ones to Claude or GPT with full context. JOSH: That cuts cost without making the system dumber. ERIK: It makes it smarter because you're matching the tool to the job. Also log the decision at each tier. If tier two routes badly, you need to see that. If tier three saves the day, capture the pattern and move it down the ladder later. JOSH: So today's tip is basically don't pay genius rates for intern work. ERIK: Exactly. Build the ladder. Measure the handoffs. Promote patterns downward. That's your tip. Use it. [pause] JOSH: We also drop daily market picks and automation tips on YouTube — search Build or Be Replaced. [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.