Build or Replaced
Today: AWS Acquires DuckLabs | Taylor Farms: How One Company's Reach Became a National Risk | CoMaps: The Offline App That Guided Rescuers Without a Signal in Venezuela Episode date: 2026-08-27.
Download MP3 →JOSH: It's Thursday, August 27. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: Today is about ownership. Who owns the tools, who owns the data, and who gets replaced when the platform changes terms. JOSH: Stick around — Erik's got an AI pro tip at the end about making agents ask for proof before they touch production. [pause] JOSH: First headline. AWS is acquiring DuckLabs. That’s the team behind DuckDB. Why does that matter? ERIK: DuckDB became the little database that engineers actually use. Local analytics, fast files, no giant warehouse ceremony. AWS buying DuckLabs tells you embedded analytics is now infrastructure, not a side project. JOSH: Second one. Mechanical Turk is shutting down September 30. ERIK: That one is poetic. Amazon called it artificial artificial intelligence, then AI ate the tasks. If your workflow depends on random humans clicking boxes for pennies, your architecture just got a calendar invite. JOSH: Third headline. Nvidia and Hugging Face. ERIK: ScanBrief flagged it as an acquisition, but the reports are messier. Talks, valuation around 13 billion, no official close. Still huge. Hugging Face is where a lot of model culture lives, and Nvidia already owns the hardware conversation. [pause] JOSH: Let’s start with DuckLabs. I feel like DuckDB went from nerd favorite to everywhere pretty fast. ERIK: That’s exactly what happened. DuckDB is what engineers reach for when they have files, parquet, CSVs, local data, and no patience for standing up a whole data platform. It runs in-process. You can stick it inside a Python script, a CLI, a notebook, a web app, whatever. It made analytics feel like SQLite for columnar data. JOSH: And AWS wants that inside its world. ERIK: Of course they do. AWS sells the big machinery. Redshift, Athena, Glue, S3, EMR, all the pieces. But a ton of real work happens before the big machinery. Someone has logs on disk. Someone has exports from a vendor. Someone has telemetry files and needs an answer in 90 seconds. [beat] ERIK: DuckDB owns that moment. JOSH: Is that good for developers, or is this one of those “open source gets absorbed” things? ERIK: Both. The announcement says DuckDB stays MIT licensed and the foundation keeps stewardship. That matters. But the practical concern is gravity. When a project joins AWS, the center of gravity shifts. Docs start pointing toward AWS paths. Integrations get first-class treatment. Priorities slowly follow the buyer. JOSH: That sounds familiar. ERIK: Yeah. Nobody wakes up and says, “Today we ruin the thing developers love.” It’s usually death by roadmap. One tiny enterprise feature. One managed service wrapper. One authentication story that works beautifully if you already live inside AWS. JOSH: Where would you use DuckDB in your own stack? ERIK: ScanBrief is the obvious one. Today it scored 96 items across 56 sources. That is exactly the kind of workload where I don’t need a giant warehouse. I need to dedupe feeds, score items, keep history, query patterns, and move on. [beat] ERIK: If I have a local artifact from a run, DuckDB is perfect. Read the file, ask the question, ship the answer. No committee meeting. JOSH: So what’s the builder lesson? ERIK: Keep your data portable. Parquet, JSONL, SQLite, DuckDB files, boring formats. Boring is good. If your entire product only works because a managed service is feeling generous this month, you don’t own much. JOSH: That’s the part people ignore. ERIK: They ignore it until pricing changes, auth breaks, rate limits move, or a product gets folded into something bigger. Then everyone gets very interested in architecture. [beat] ERIK: PrimeBus is built around that lesson. Events go on NATS. Telemetry is emitted by projects. I can change consumers without asking the producers to care. That’s not fancy. That’s survival. JOSH: PrimeBus had a big number this morning too, right? ERIK: Yep. The auto-merger has run 2295 attempts since June 5. 1507 merged, 788 blocked by Gandalf, 0 escalated to me. That blocked number is the important part. Guardrails did their job. JOSH: Wait, really? Zero escalated? ERIK: Zero. Which doesn’t mean zero problems. It means the system knew when not to be cute. [pause] JOSH: That connects pretty cleanly to Mechanical Turk shutting down. ERIK: It does. Mechanical Turk was basically a human API. Send tiny tasks in, get tiny answers out. Label this image. Compare these two records. Moderate this text. Validate this result. JOSH: And now Amazon is ending it. ERIK: September 30. And honestly, it makes sense. A lot of those tasks are now model calls. Some of the human workers were reportedly using AI anyway, which is hilarious and also completely predictable. JOSH: The humans automated the human layer. ERIK: Of course they did. That’s what humans do when the work is repetitive and the pay is bad. [beat] ERIK: But here’s the real point. Human-in-the-loop doesn’t go away. Cheap human-in-the-loop goes away. JOSH: What replaces it? ERIK: Smaller, better human review loops. You don’t need a crowd for everything. You need escalation when confidence is low, when money moves, when legal exposure exists, when a customer gets touched, or when production changes. JOSH: So not “ask a human every time.” ERIK: Correct. That’s just manual work wearing a lab coat. The better pattern is model first, policy second, human only when needed. And the human should get context. Not “is this good?” That’s useless. Give them the diff, the tests, the logs, the confidence, the blast radius. JOSH: That sounds like Gandalf. ERIK: Exactly. Gandalf is the reviewer in the middle of the PrimeBus pipeline. Claude can propose fixes. Tests can pass. But the policy layer still blocks things. Secrets, weird file paths, risky commands, broad edits, anything that smells wrong. [beat] ERIK: That’s the part people miss with agents. The model is not the system. The system is the model plus the harness plus the rules plus the evidence. JOSH: What does this mean for teams that still use outsourced review or labeling? ERIK: Start mapping where humans actually add judgment. If they’re just reading a field and clicking yes or no, that task is probably done. If they’re resolving ambiguity with business context, keep them, but make the machine prepare the case. JOSH: Give me an example. ERIK: PrimeDistro is a good one. It can scrape businesses, audit whether they have a website, generate a preview site, and prepare outreach. But if a business looks borderline, I don’t want the agent guessing forever. I want it to package the evidence. Screenshots, domain status, Google listing, proposed postcard. Then a human can approve fast. JOSH: That’s a very different job. ERIK: Better job, too. Nobody wants to be a CAPTCHA with a pulse. [beat] JOSH: Dry, but fair. ERIK: It’s true. If your company’s human process is just slow pattern matching, AI is coming for it. If your human process is judgment, accountability, and exception handling, AI should make it cleaner. JOSH: What’s the risk? ERIK: The risk is pretending the model is confident because the text sounds confident. That’s how you get bad labels, bad merges, bad customer emails, and weird support tickets at 2 AM. [beat] ERIK: Ask me how I know. JOSH: I feel like I shouldn’t. ERIK: Correct instinct. [pause] JOSH: Now Nvidia and Hugging Face. You said the signal was messy. ERIK: Yep. Some reports say agreed, some say talks, and there’s no official confirmation from both sides that I’d treat as final. So the responsible take is this: the acquisition may not be closed, but the pressure is real. JOSH: Why does Hugging Face matter that much? ERIK: Because Hugging Face is not just a website with model files. It’s where developers discover models, compare them, publish datasets, test ideas, and build around open weights. It became the town square for AI builders. JOSH: And Nvidia already owns the GPU side. ERIK: Nvidia owns the oxygen tank in the data center. If they also influence the model distribution layer, that’s a serious amount of control. Hardware, libraries, inference paths, model hosting, developer mindshare. That is not small. JOSH: Is that bad? ERIK: It depends on what they do. Nvidia has earned its position by executing. CUDA, drivers, libraries, developer support. Painful sometimes, but the stack works. The concern is neutrality. Hugging Face works because AMD users, Intel users, Apple users, researchers, hobbyists, startups, everybody feels like they can show up. [beat] ERIK: If it starts feeling like the lobby of an Nvidia conference, that changes the culture. JOSH: What should builders do with that information? ERIK: Don’t build your entire AI workflow around one hosted surface. Pull the models you depend on. Track licenses. Keep evals local where you can. Know how to run at least one fallback model outside your favorite provider. JOSH: You actually do that? ERIK: Yeah. The Bobaverse fleet has 12 agents right now. Neo, Homer, Bill, Echo, Gandalf, Claude plus GPT. I don’t want one provider outage or one API behavior change freezing the shop. JOSH: That sounds expensive. ERIK: It can be. But being stuck is expensive too. Pick your poison. I’d rather pay for enough redundancy than explain why the business stopped because one model endpoint got moody. JOSH: How does model choice change in that world? ERIK: You stop asking “what’s the best model?” That question is lazy. Ask what the job is. Coding? Use the model that writes correct patches and follows repo patterns. Research? Use the model that cites and separates facts from guesses. Fast classification? Use the cheap fast one. Risky production change? Use two models and a policy gate. [beat] ERIK: Model selection is routing. Treat it like network engineering. JOSH: That’s very you. ERIK: It’s true. Packets don’t care about your feelings. Workloads don’t either. Route based on latency, cost, reliability, and blast radius. JOSH: Where does Hugging Face fit for local builders? ERIK: It’s the parts store. You go there to find the model, grab the tokenizer, read the card, check the license, see community issues, maybe test a quantized version. If that parts store changes ownership, you keep shopping there, but you also keep copies of the parts you need. JOSH: So the move is not panic. ERIK: No. Panic is for people without backups. Builders should inventory dependencies. Which models? Which datasets? Which APIs? Which licenses? Which local runtimes? If Hugging Face vanished for a week, what breaks? [beat] ERIK: Answer that before the outage, and you look like an adult. [pause] JOSH: Quick thread between all three stories. AWS and DuckDB, MTurk shutting down, Nvidia circling Hugging Face. What’s the pattern? ERIK: The pattern is that the middle layer is being bought, closed, or replaced. Local analytics became strategic. Human microtasks got eaten by models. Model distribution is valuable enough for massive acquisition talk. JOSH: Meaning? ERIK: Meaning builders need ownership at the edges. Own your data formats. Own your event flow. Own your evals. Own your fallback paths. You don’t need to own every chip or every model, but you need to know where the exits are. JOSH: That’s less glamorous than a new tool demo. ERIK: Good. Glamour doesn’t restart services. PrimeDash tells me 146 services are running on the production server right now. That number matters more to me than a keynote. A keynote won’t tell me which service is wedged. JOSH: That’s the most Erik sentence possible. ERIK: Fine by me. [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 produce an evidence packet before it changes anything important. Not a paragraph saying “I think this is safe.” Evidence. [beat] ERIK: For code, require the exact files changed, tests run, test output, risk level, rollback path, and why the change is scoped. For infrastructure, require the target device, command preview, expected state, current state, and a no-change dry run if the tool supports it. JOSH: So the prompt is basically asking for proof. ERIK: Yep. Here’s the simple version. “Before taking action, produce an evidence packet. If any required evidence is missing, stop and ask. Do not infer success. Use tool output only.” [beat] ERIK: That one line saves pain. Models love sounding finished. Systems need proof. That’s your tip. Use it. [pause] JOSH: Track your freedom score and net worth with the Freedom Blueprint app — free download, link in the 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.