A Fix the Agent Can't Run on Its Own Is Not a Fix
If your autonomous system fails and your 'fix' is to do the job by hand, you didn't fix it. You just did it once.
Bugs, failures and making things hold up.
If your autonomous system fails and your 'fix' is to do the job by hand, you didn't fix it. You just did it once.
Every layer of a modern web stack — Postgres on Supabase, Node on Vercel, the Zoom API, JS date parsing — defaults to UTC. If your business runs on Ea
The platform's liveness probe and your external uptime monitor need different endpoints. Bolt deep checks onto the wrong one and a dead API key will
I ran a full audit on two production Next.js apps and found 12 of 24 server action files were passing raw form data straight to Postgres. Zero Zod.
Some destructive-but-bounded operations are legitimately 'traced-only' — not because you were lazy, but because that's the honest shipping posture. The
Shopify stores order numbers as #472791. If your query strips the # from user input but matches with .eq(), you'll never find anything. Match
Passed a raw JS Date object to postgres.js (my Postgres client) as a query param. The driver threw ERRINVALIDARGTYPE. The rate limiter that
If your error handler calls res.json() and then res.text() as a fallback, the fallback silently throws 'Body has already been read' — and the real
Validating at the form layer feels like enough — until you ship. Validate once, at the trust boundary, every time.
I was fetching all 859 facility rows from the database on every single chat message and filtering in JavaScript. One function call fixed it — ~8x le
If your background process returns nothing and throws no error, you have no idea if it worked. Make noise the default — before you do anything else.
Your API client timeout must live under your platform's hard ceiling — not above it. And retrying a 4xx just burns the budget twice.
Switching from row-by-row upserts to 100-row batches in our Shopify → Supabase orders sync cut API round-trips by ~50×. The fix was five lines. The
Don't put loading='lazy' on your LCP element. Lazy-load everything below it, and serve the hero/LCP image via your CDN's transform API — pre-siz
If you're writing coercion glue so data can pass your own validator, the validator is the problem.
Retry with backoff + draft persistence are the two things you add to any chat that talks to an LLM. One handles network flakes. The other means user
I spent two deploys guessing at the wrong things. One targeted diagnostic commit found it in minutes. The bug was a timezone offset — server-rendere
When your upstream data is corrupted, stop trying to clean it. Find a reference in your own system that you know is correct, and derive everything fro