All articles
4 part series

Vibe Coding Basics

Plain explanations of the things an AI builder sets up for you and then never explains: row-level security, edge functions and API keys, and what actually belongs in a privacy policy and terms of service.

  1. Enabling RLS and writing a policy are two different switches, USING and WITH CHECK do two different jobs, and the service role ignores both. A plain explanation of the feature your builder set up.

  2. Anything the browser can send, a visitor can read. What an API call is, why a key in frontend code is already public, what an edge function does about it, and when you genuinely need one.

  3. A generated policy naming services you do not use is worse than none: it is a written claim that is false. The sections a privacy policy needs, and how to find what your app actually collects.

  4. Most of a terms document is boilerplate and a few clauses carry the weight. What each clause is for, which ones courts have thrown out, and how people agree to them in a way that holds.