How I Stopped Fighting Vercel Errors Blind
when your Vercel function returns a blank 500, the first fix is rarely the bug — it's making the function tell you what went wrong. Surface the error,
A lab notebook: what I'm learning while building with AI, written as I go.
when your Vercel function returns a blank 500, the first fix is rarely the bug — it's making the function tell you what went wrong. Surface the error,
Don't save every turn. Don't wait to be asked. Separate the cheap decision ('is this worth keeping?') from the expensive write ('format it, dedup it
Blind retry is almost always wrong. Classify the error first, fix what you can, then retry — and narrate loudly so you know what's happening.
Telling an LLM not to use a tool is not the same as preventing it from using the tool. Enforce scope at two layers — prompt AND harness — or the fir
Put your TTS behind a proxy URL endpoint. Use <Play> not <Say>. Swap providers without touching telephony.
Dropped a literal {channelid} placeholder into a Python f-string to guide an LLM. Python treated it as a variable, crashed every run, and my agen
When an AI agent has side effects — creating tasks, sending messages, triggering anything — a prompt saying 'don't do X' is not a hard stop. You nee
I assumed I knew the shape of an external API response. I was wrong. 849 locations got corrupted before I noticed. The fix is boring — run the live quer
Build your OAuth callback server so it can be fed the redirect URL by hand over loopback. Tunnels are flaky. Auth codes survive a 502.
The PII leak that almost shipped wasn't from an attacker. It was from me. A console.log I left in while debugging.
When an OAuth provider rotates refresh tokens, you must write the new one back to disk on every single refresh. Read-once-from-.env quietly breaks
If you have an AI chat endpoint and no body size cap, you have a denial-of-wallet hole. Cap it in your app — not your platform. 256 KiB is a reas
I built a lead gate for a cancer clinic finder that turned the AI into a bouncer. 71% of users hit one sentence and left. The fix was three words: lead
The gate that was supposed to capture leads was the reason people were leaving. Flip the order — lead with value, catch them on exit — and your moda
Don't silence react-hooks/set-state-in-effect with eslint-disable. It's the lint telling you your SSR will break. The real fix is useSyncExtern
The Setup
Adding .env to .gitignore does nothing if git is already tracking the file. The actual fix is git rm --cached .env. Everything else is just wi
supabase-js's .ilike() passes your string directly as a PostgreSQL LIKE pattern. PostgREST exposes no ESCAPE clause. Strip % and from
If an upstream API call fails and you surface that error straight to the client, you're leaking. Log the detail server-side. Return a sanitized gen
Anything launched by something other than you-in-the-project-dir — MCP server, launchd daemon, cron job — must resolve .env relative to import.me
A blunt AI gate doesn't protect the product — it wrecks the funnel. The fix is a short block list and a generous allow list, not a wall.
In Next.js App Router, generateStaticParams is NOT a whitelist. Drafts you exclude from the list are still publicly accessible by default. One lin
Obsidian's markdown flavor (![[image.png]], [[wikilinks]]) doesn't render on the web. A small translation layer fixes it, and suddenly your note
I assumed I knew the shape of a TakeShape API response. I was wrong. 856 of 859 cancer treatment centers silently lost their addresses. Fixed in one com
Next.js's file tracer can't follow dynamic import specifiers — so native packages that resolve their binary at runtime get silently excluded from yo
When a matter transitions to Active, fire your full file ecosystem — Drive folders, Gmail label, Xero project — in one burst from inside the app. But re
If you're auto-importing nodes into a React Flow canvas, derive position from an index. Never accumulate per-node offsets — they compound into an un
When you batch LLM calls to generate dense structured output, four things will break on you — and they'll break in sequence, one crash at a time. He
Don't put secrets in the prompt. Stripping sensitive fields from your system prompt JSON is the real lock — 'do not share this' instructions are def
Shopify silently drops any Liquid section whose {% schema %} name field exceeds 25 characters. The error you see looks like a missing file. The -