Ship Your App
Shipping software now starts before you can write code. The constraint has moved from building the thing to knowing whether what you built holds up. Covers building with AI assistance, from first prototype to the checks that decide it's ready for real users.
Latest in this section
Tools for this →Fable 5.2 Vibe Coding: From Demo to Product People Trust
Fable 5.2 vibe coding gets you a working demo faster than ever. What the model's own docs warn about, and the five gates between that demo and a real product.
Nov 11, 2026 · 12 min read
Client-Side vs Server-Side Validation: Which of Your App's Checks Are Real
Client side vs server side validation comes down to control: your user can change the browser, so a check enforces nothing until your server decides it too.
Nov 9, 2026 · 9 min read
How Easily Can Someone Get Around a Front-End Check?
You can bypass client side validation with tools built into the browser: edit a field's value, turn off JavaScript, or send the request yourself.
Nov 9, 2026 · 6 min read
"Never Trust the Client" — What That Actually Means for Your App
Never trust the client means re-verifying anything that matters — money, someone else's data, access — on your server, using a value it controls itself.
Nov 9, 2026 · 6 min read
Why Your App Should Never Take the Price From the Page
Client side price manipulation happens when checkout trusts a browser-sent price instead of looking it up by product ID on the server, every time.
Nov 9, 2026 · 6 min read
The Server-Side Check That's Still a Browser Decision
A quiet entry among server side validation mistakes: the check runs on your server but trusts the number the browser sent instead of looking it up itself.
Nov 9, 2026 · 6 min read
Moving a Key Isn't Fixing It: When You Actually Have to Rotate
Here's how to rotate an API key: issue a new value and turn off the old one. Moving or renaming a leaked key doesn't fix it — it's still live and dangerous.
Nov 2, 2026 · 9 min read
You Deleted the Key. It's Still in the Git History.
An API key committed to git stays in every past snapshot even after you delete the line — reachable by anyone who cloned the project before your cleanup.
Nov 2, 2026 · 7 min read
Publishable vs Secret Keys: They Look Identical and They Aren't
Publishable vs secret key: they're built for two different jobs and often look identical — mixing them up can break features or expose what shouldn't leak.
Nov 2, 2026 · 7 min read
The .env File Did Not Make It Private
Is my .env file secure? The name tells you it holds settings, not that it's stayed private — a key that's ever been reachable still needs to be rotated.
Nov 2, 2026 · 7 min read
Which Keys to Rotate First When You're Not Sure What Got Out
Which keys to rotate first when time is short: unknown-location keys, then currently-reachable secrets, then anything past-exposed and never rotated.
Nov 2, 2026 · 7 min read
Supabase Row Level Security: What "RLS Enabled" Does and Doesn't Do
Supabase row level security 'enabled' means Postgres checks a policy before it hands over a row. It doesn't mean the policy keeps anyone out.
Oct 19, 2026 · 8 min read
RLS Is Enabled and Your Data Is Still Readable
RLS enabled but not secure means a policy exists and never ties the row to the person asking. Five conditions that admit everyone, and how to spot them.
Oct 19, 2026 · 7 min read
Supabase RLS Policies, One Operation at a Time
Supabase RLS policies run per operation: select and delete use USING, insert uses WITH CHECK, update uses both. SQL for each, and where they overlap.
Oct 19, 2026 · 7 min read
The Anon Key Is Public. The Service Role Key Ends the Argument.
Anon key vs service role key: Supabase now calls them publishable and secret. One is public and bound by your policies. The other skips them entirely.
Oct 19, 2026 · 6 min read
How to Check What a Stranger Can Actually Reach in Your Tables
How to test Supabase RLS: rule out the secret key, run the Security Advisor, then try all four operations as a signed-out visitor and as another user.
Oct 19, 2026 · 7 min read
Authentication vs Authorization: Logging In Isn't Permission
Authentication vs authorization: logging in proves who you are, but it doesn't prove you're allowed to touch this record. Here's the difference.
Oct 15, 2026 · 8 min read
Broken Access Control, Explained Without the Jargon
Broken access control means an app decided who can reach what based on the wrong check — usually 'signed in' instead of 'is this yours.'
Oct 15, 2026 · 6 min read
Changing the Number in the URL: What IDOR Actually Is
IDOR explained: it happens when a record's id comes straight from the request and nothing checks whether it actually belongs to the person asking.
Oct 15, 2026 · 6 min read
Whose Record Is This? The Check Most Apps Skip
To check record ownership, compare a record's owner field to the current session's user id before returning or changing it — most routes skip this.
Oct 15, 2026 · 7 min read
When "Signed In" Is Doing a Permission Check's Job
Signed in is not authorization — a login proves you're a real user, but a permission check proves you're allowed to touch this specific record.
Oct 15, 2026 · 6 min read
Vibe-Coding Security: Making an AI-Built App Safe for Real Users
Vibe coding security means closing the gaps AI builders skip — exposed secrets, client-only auth, no rate limits, no cost caps, and leaky errors.
Sep 10, 2026 · 8 min read
Is Your App Actually Production-Ready? A Pre-Launch Check
Is my app production ready? Run six yes/no checks — secrets out of the browser, server-side auth, rate limits, cost ceilings, sanitized errors, monitoring.
Sep 10, 2026 · 5 min read
The Vibe-Coding Mistakes That Bite You After Launch
Vibe coding mistakes repeat in a predictable set — secrets in the client, frontend-only auth, no rate limits, editable paywalls, and leaky errors.
Sep 10, 2026 · 5 min read























