- Debugging
- Cursor
How to debug Cursor-generated code when Cursor can’t.
When Cursor can’t fix its own bug: use git to see what it changed, bisect to the breaking edit, and check the four places Cursor code usually fails.
Read
9 min read
Notes from the messy middle
Guides to debugging and shipping AI-generated code
Practical, step-by-step writing for the point where a prototype becomes a real product: why generated code breaks at the seams, why an app works locally and not in production, and what “production ready” actually means. Every guide answers the question in its first paragraph.
8 articles shown.
- Code review
- AI-generated code
How to review AI-generated code without reading every line.
Review generated code by risk, not by file: authorization and data writes first, six greps for common failures, and the seams where pieces meet.
Read
9 min read
- Security
- AI-generated code
How to secure an AI-generated app before real users touch it.
The eight security problems that recur in AI-generated apps, from missing ownership checks to leaked secrets — with a fix and a test for each one.
Read
10 min read
- Codebase rescue
- Legacy code
How to take over an existing codebase nobody understands.
Inherited code nobody understands? A five-day method: map it before changing it, find the load-bearing parts, then decide what to touch and what to leave.
Read
9 min read
- Finishing
- AI-generated code
- Launch
How to finish an AI-built app that’s stuck at 80%.
The last 20% of an AI-built app is integrations, edge cases and deployment. Take an honest inventory, wire real payments and auth, and get it live.
Read
9 min read
- Debugging
- AI-generated code
Your AI-generated code isn’t working. Here’s how to find out why.
A practical method for debugging AI-generated code when prompting has stopped helping: reproduce it, read the seams, check the assumptions, and fix the cause.
Read
8 min read
- Deployment
- Production
It works locally but not in production. Here’s the checklist.
Nine differences between your machine and production, in the order they break: env vars, build output, ports, database, CORS, paths, time, memory and secrets.
Read
9 min read
- Production
- Security
- Launch
Is my vibe-coded app production ready? A 12-point check.
Working is not production ready. Twelve checks: backups, authorization, secrets, error visibility, rate limits and rollback — and what each costs if skipped.
Read
10 min read
Your AI-built app doesn’t need another prompt.
Sometimes it needs an engineer.
Send the messy version. That’s usually the useful version.