Writing
The Supabase mistake that exposes your data
Filtering data in your queries and hiding it in the UI feels secure. Without Row Level Security, anyone with your public anon key can read the whole table.
Read →I almost listed a product I never built
A fake-door landing page is a great way to test demand. It is not a product. Calling it one costs the trust that building in public runs on.
Read →I audited my own online presence. It was a mess.
Three profiles, three different people, none of them the one actually building. Your profiles are your storefront, and mine contradicted each other.
Read →Your Next.js Server Action is a public endpoint
A server action looks like a function call, but it compiles to a public POST endpoint anyone can hit with any arguments. Authenticate and validate inside it.
Read →What actually ends up in your Next.js client bundle
NEXT_PUBLIC env vars and anything a client component imports ship to the browser. One import line can leak a secret. The server-only package makes it impossible.
Read →Verify your Stripe webhooks, or anyone can grant themselves Pro
An unverified webhook endpoint is a public URL that upgrades accounts. Without signature verification, anyone can POST a fake checkout.session.completed and unlock your paid plan.
Read →