The Migration Was Perfect. The Table Was Empty. Here's Why.
Supabase auto-enables Row Level Security (RLS) on every new table — no policy = deny-all, and supabase-js returns { data: [], error: null } with
A lab notebook: what I'm learning while building with AI, written as I go.
Supabase auto-enables Row Level Security (RLS) on every new table — no policy = deny-all, and supabase-js returns { data: [], error: null } with
If your CSS variables use cqi units, never apply them to html — even inside a shared html, body {} rule. Set font-size on body only. One m
A one-line migration comment asserted 'no SKU overlap between stores.' It was wrong. Every velocity, forecast, and ledger report in the supply chain
If your daily sales chart shows weekend zeros on warehouse-fulfilled orders, you're almost certainly bucketing by the wrong timestamp — and your timezon
React Compiler owns memoization now. When its eslint rules flag a useMemo, delete the annotation first — don't eslint-disable. Nine times out of te
CSS grid items default to min-width: auto. If one column holds a <pre> block with long lines, the whole layout blows past the viewport. Fix: mi
PostgREST silently caps query results at 1000 rows. No error. The data shape looks fine. Your math is just… wrong. Move aggregation into SQL functions c
Never set font-size on html. cqi on the root element resolves against the viewport, not a container — and it will silently detonate every rem-ba
Before shipping a single feature chart, scaffold your shared primitives — palette, container, tooltip styles, selectors. Every styling bug you hit a
Client-side AES-256-GCM keeps honest people honest. It is NOT a substitute for real access control at the data layer. Know exactly what you bought.
Texting 'call me' to my AI agent now rings my actual phone. Getting there required three non-obvious decisions I'll make again on every agent I build.
Xero returns undefined for amounts on untouched projects. Feed that into a currency formatter and you get $NaN. One ?? 0 fixes it. But the sam
One auth check isn't defense-in-depth. Mirror it at the API handler, the middleware, AND the route layout — and make every gate fail closed when the
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
I called the advisor before shipping an Airtable data migration — it caught real blockers. Same week I skipped that step on a Shopify sync, and a 30-sec
Don't cache cheap, user-mutable reads in a long-lived execution context. The staleness cost will eat you alive.
If you use supabase-js's .ilike() for lookups, % and in the input are live PostgreSQL wildcards — and PostgREST exposes no ESCAPE clause t
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.
Cold-start bugs don't live in your shell — they live in the real launch environment. You can't find them until you run there.
Neither pure semantic search nor pure keyword search is enough. You need both, fused — and I had to build each one twice to figure that out.
maxtokens=4096 silently truncates complex structured outputs. The model calls the tool, you get an HTTP 200, and the field is just… empty. Log
In any processing loop, 'transient' and 'terminal' are completely different states. Only terminal states should block re-processing — and they definitel
React does NOT block javascript: URLs in <a href>. If you're pulling URLs from a database, you need a scheme check before render. Every time.
When you ask an LLM to produce a schema mapping, prompt clarity isn't enough. Validate at the boundary and halt loudly — or you'll get silent, empty row
A HARDRULES block I wrote to protect financial data was killing aggregate financial questions too. The fix wasn't removing the rule — it was sco
Two layers of failure hid a display name from my calendar agent. The fix wasn't patching either layer — it was checking a completely different system th
React 19 resets uncontrolled form fields after a server action returns — on success and on non-throw failure. The DB write lands fine. Only the UI
react-hooks/set-state-in-effect fires as a hard error in Next.js 16. Three of my four cases had cleaner fixes. The fourth was legitimately right t
If a Supabase helper creates its own createClient(), it has no session. RLS rejects the read. It fails silently. Everyone gets denied. Pass the