Test runs, builds and services print far more than anyone reads. Coding agents read it anyway, all of it, and pay for every token. Then they read it again after the next change. The common fix is to have a language model summarise the output, but a summary can drop the one line that mattered, and it won't tell you what it left out. Abbreviatory takes the opposite approach. It … [Read more...] about Abbreviatory Shrinks a 5.6 MB Log to a 3 KB Report for Coding Agents Without a Language Model
Projects
Bootstrapping Updates an Application’s Seed Data on Every Release Without Overwriting Admin Edits
Every application ships with rows it needs to run. Roles and permissions. Plan tiers. Workflow states. Country and currency lists. Email templates. They change with each release, and customers' admins edit them too. Then comes the upgrade, and somebody's careful edit gets wiped, or the change the release was supposed to make never lands. Bootstrapping keeps that reference data … [Read more...] about Bootstrapping Updates an Application’s Seed Data on Every Release Without Overwriting Admin Edits
jvq Fails the Pull Request That Makes Your Code Slower and Its Sister Tool Queries JSON Lines 19 to 31 Times Faster Than jq
Code gets slower one pull request at a time. Nobody means it. A small change here, a convenient library there, and each one passes review because nobody measured it. Months later the product is noticeably slower and there's no single change to blame. jvq measures every one. It's a performance budget gate for CI: it runs your benchmarks on the base branch and on the change, … [Read more...] about jvq Fails the Pull Request That Makes Your Code Slower and Its Sister Tool Queries JSON Lines 19 to 31 Times Faster Than jq
LQO Finds the PostgreSQL Queries the Planner Gets Wrong and Proves Which Setting Makes Them Faster
Some PostgreSQL queries are slow without being big. The planner picks plans from estimated row counts, and those estimates can be off by a factor of a thousand, often because two related columns are invisible to the statistics. A query that should take 40 milliseconds takes four seconds. A good DBA knows the fix routine: run EXPLAIN ANALYZE, find the bad join, try … [Read more...] about LQO Finds the PostgreSQL Queries the Planner Gets Wrong and Proves Which Setting Makes Them Faster
FlowChassis Runs Multi-Step Jobs in Go That Resume After a Crash and Undo Themselves on Failure
Plenty of jobs come in steps that have to finish together or not at all. An order reserves stock, charges a card and books a courier. A sign-up creates an account, sets up billing and sends a welcome email. A device update downloads, verifies and installs. The risk is always the same: the process dies halfway, and you're left with a charged card and no courier. There are two … [Read more...] about FlowChassis Runs Multi-Step Jobs in Go That Resume After a Crash and Undo Themselves on Failure
Multivergence Gives AI Agents Forkable State to Try Several Plans Before Committing to One
Good agents, like good planners, keep options open. A coding agent tries three fixes for a bug. A travel agent holds four venue bookings until the client decides. An on-call agent weighs competing explanations for an outage while the evidence trickles in. The trouble is where those alternatives live. Usually in the prompt, which isn't state at all, or in full copies like git … [Read more...] about Multivergence Gives AI Agents Forkable State to Try Several Plans Before Committing to One
Inorderly Puts Late, Duplicated and Out of Order Events Into One Sequence That Replays Byte for Byte
Events rarely arrive in the order they happened. Webhooks get retried, so the same event shows up twice. Device clocks drift, so a payment looks older than the order it paid for. A market feed handler sees tick 88 before tick 87. Most teams patch it with a dedupe table, a sort buffer and a timeout, and the patch mostly works. The trouble shows up on the second run. A backfill, … [Read more...] about Inorderly Puts Late, Duplicated and Out of Order Events Into One Sequence That Replays Byte for Byte
CodeInstances Keeps a Program Run as a File You Can Replay Offline, Compare and Shrink
Code is versioned, reviewed and kept for years. Its runs are thrown away. When a run fails, it leaves a log line and a guess. A CI test fails at 3 a.m. and the run is stuck on one machine. An API answered oddly once and never again. A maintainer gets an issue saying "sync breaks against our account" and has no way into the reporter's account. CodeInstances keeps the run. It … [Read more...] about CodeInstances Keeps a Program Run as a File You Can Replay Offline, Compare and Shrink
TaskFused Runs Duplicate Requests Once and Shares the Result With Every Caller
Work gets asked for more than once all the time. A user double-clicks Export. A client times out and retries while the first request is still running. Ten dashboards ask for the same monthly report at nine in the morning. Each copy burns the same CPU, the same API calls and the same database load, and sometimes the copies get in each other's way. With paid AI model calls or … [Read more...] about TaskFused Runs Duplicate Requests Once and Shares the Result With Every Caller
RadarModel Warns You When an AI Model Your App Calls Is Retired or Your Database Schema Drifts
Apps call AI models by name, and those names don't sit still. Providers retire models, rename them, shrink context windows, add retirement dates and change token prices. Each change is announced somewhere different: a changelog, a deprecations page, an email that went to someone who left. Most teams find out when a request fails in production. Databases have the same problem in … [Read more...] about RadarModel Warns You When an AI Model Your App Calls Is Retired or Your Database Schema Drifts