Posts
All the articles I've posted.
Stripe Holds the Subscription. Your Database Holds a Copy.
Subscription state, idempotent Stripe webhooks and tenant scoped billing tables drawn from multi-tenant platform and ledger work.
The Policy Was Enabled. One Role Still Read Across Tenants.
Auditing Supabase Row Level Security for a multi-role SaaS pilot, testing tenant isolation role by role with the service key outside the test path.
The App Balanced the Ledger. The Database Refused the Write.
Enforcing double-entry balance, integer minor units and append-only audit in Postgres with constraints that refuse the forbidden write.
I Could See Every Resource. I Still Could Not Rebuild It.
Taking over cloud infrastructure someone else built, and why a read-only inventory answers the easy question rather than the one that decides the handover.
The Device Went Quiet. Quiet Is Not a Reading.
A thousand devices reporting over MQTT taught me that absent telemetry is ambiguous, and that the ambiguity gets worse the moment the device is allowed to move.
The Browser Never Sees the Token. The Edge Function Holds It.
Read-only social API integration through Supabase Edge Functions in Deno and TypeScript, with tokens sealed server side and scoped to the minimum.
Nobody Typed the 10,000 Lines. The Review Belonged Upstream.
In a generated system the unit of review is not the output, it is the template that emitted it, because a defect there ships in every instance at once.
The App Called OpenAI Directly. The Gateway Should Have Been in Between.
Putting a Go gateway in front of a Python RAG service to route across providers, stream safely, enforce per-customer budgets and cache without hiding failures.