08 READ
Blog
Articles, field notes, and honest opinions from the EDB team.
- deep-dive
Why We Run Multiple LLMs (and Make Them Argue)
One model gives you one confident answer. The problem is "confident" and "correct" aren't the same word.
- deep-dive
Stop Re-Asking the LLM the Same Question
Incremental distillation: hash the inputs, skip unchanged checks, and cut ~64% of LLM calls on an unchanged re-run — with an honest note on what is not gated yet.
- deep-dive
Heuristics + AI: Why Deterministic Rules Come First
The cheapest, most accurate part of Swordfish doesn't use AI at all. That's not an accident.
- essay
Teaching an Audit Tool to Remember
Cross-audit lineage and supersession: immutable history, and the what-changed-since-last-time report a returning user actually wants.
- deep-dive
The Stuff That Isn't in the Code: Inferred Knowledge and Why Migrations Lose It
Your application knows things it never wrote down. The migration is where it forgets.
- essay
A Tour of the Swordfish Sample Apps (and What Breaks in Each)
The hardest part of evaluating a database migration tool is finding something honest to point it at.
- essay
Welcome to Goldfish
EDB ships open-source software, sample code, tutorials, and one-click infra for developers — without adding to the noise.
- deep-dive
Cheap Checks Before Expensive Ones: The Two-Part Judge Pattern
The two-part judge pattern in ~40 lines: a deterministic filter first, multi-model consensus second. It generalizes to RAG, extraction, and code review.
- essay
Why agent memory belongs in Postgres
A vector store is an index, not a database. Agent memory needs both — and pgvector is the door.
- opinion
Swordfish: A Harness for Your Copilot, Not Migration-in-a-Box
We're not trying to replace your LLM. We're trying to make it stop guessing.
- essay
I Asked an LLM to Diagnose My Database. Then I Asked Another LLM if It Was Lying.
The origin story of the judge: the model invented a shared_buffers value. The fix was not a bigger model — it was cheap grounding plus a second-opinion jury.
- opinion
Why Database Migrations Are a Developer Problem
The schema is the easy part. The code is where migrations go to die.
