Free workshop: build with AI without losing control of your project View the workshop →
vibebusters

// the glossary

The glossary

Each term gets a plain definition, then what it changes in an app built with Lovable, Bolt, Claude Code or another AI tool, and how to check it.

Environment variables

Environment variables are settings passed to an application when it starts or is built, instead of being written into the code: database address, service keys, test or production mode. They let the same code run in several environments and keep secrets out of the repository. Read the definition →

Exposed secret

An exposed secret is private access information (payment key, email key, database password, API token) that has become readable outside the place where it should live: code sent to the browser, a Git repository, a screenshot or a log. Once exposed, a secret must be treated as compromised and replaced. Read the definition →

Row Level Security (RLS)

Row Level Security (RLS) is a PostgreSQL feature that applies access rules to every row of a table, inside the database itself. On Supabase, it decides what a visitor or a signed-in user can read, create, update or delete. Read the definition →

Supabase secret key (service_role)

The Supabase secret key, called service_role in the legacy key system, grants administrator access to the database and bypasses every Row Level Security policy. It is meant for server-side processing and must never appear in code that runs in the browser. Read the definition →

Technical debt

Technical debt is the future extra cost created by quick or temporary choices in software: duplicated code, missing tests, confusing structure, ageing dependencies. Like financial debt, it lets you move faster at first, then charges interest in the form of time lost on every change. Read the definition →

Vendor lock-in

Vendor lock-in describes a situation where leaving a service is costly in time, money or risk, because the code, the data, the accounts or the features depend on it. It is not a flaw in itself: it can be measured, documented and reduced when the stakes justify it. Read the definition →

Vibe coding

Vibe coding is a way of building software by describing what you want in plain language to an AI, which writes the code. The person steers, tests and corrects through conversation, often without reading the code produced. Read the definition →