Skip to main content

Fix the Mess

Every builder ships bugs, breaks a deploy, and leaks a key at least once. Here you meet those messes on purpose — read the symptom, diagnose the real cause, and choose the fix. Stuck? The hints escalate one nudge at a time, and solving with fewer of them earns more.

Start with the free one. Guess wrong all you want — that's how the fix sticks.

Starter

A common first-timer trip-up.
Starter

Works locally, 500s in production

Server log: `Error: OPENAI_API_KEY is undefined` — yet it works on your machine.

Environment VariablesDeploymentDebugging
3–5 min
StarterPro

The deploy succeeded but the site is blank

The deploy log ends with "Build completed" but the browser console shows 404s for every `/assets/*.js` file.

DeploymentDebugging
4–6 min

Tricky

Needs a real diagnosis, not a guess.
TrickyPro

Your API key is in your Git history

A secret scanner flags `const key = "sk-live-..."` committed to your public repo.

SecurityAPI Keys
5–8 min
TrickyPro

The model returned broken JSON

`SyntaxError: Unexpected token` — the model wrapped its JSON in ```json fences.

Structured OutputJSONDebugging
5–8 min
TrickyPro

The API call just failed

`fetch failed: 503 Service Unavailable` bubbles up and crashes the UI.

DebuggingReliability
5–8 min

Gnarly

The kind of bug that eats an afternoon.
GnarlyPro

Too many requests

`429 Too Many Requests` from the model provider.

ReliabilityAPIs
6–10 min
GnarlyPro

One leaked key, every environment down

Every environment returns `401 Unauthorized` from the provider at once, right after you rotated the compromised key.

API KeysSecurityEnvironment Variables
6–10 min