About brokeinprod
Most technical writing documents the happy path. brokeinproddocuments the other one — the error at 1 a.m., the cause that took three hours to find, and the one-line fix that finally turned the build green.
Why this exists
The official docs tell you how something is supposed to work. They rarely tell you what breaks when you wire it into a real app, on a real deadline, with real data — when the example in the README meets the edge case in production. That gap, between the tutorial and the thing you actually shipped, is where this site lives.
Everything here comes from real builds. If it's on the site, it's because it broke something, cost an afternoon, or wasn't written down anywhere else clearly enough to save the next person the trip.
What you'll find here
The writing is organized around four areas:
- Security — CSP, rate limiting, auth, RLS, and the holes you open by accident.
- Hosting — where to actually run it, and what the bill does at scale.
- Debugging — the error, the cause, the fix. The stuff nobody documents.
- Full-stack — uploads, image pipelines, CRUD, multi-tenant Postgres, and everything in between.
The stack underneath most of it is Next.js, Postgres, and Vercel, with Rust and Python turning up where they earn their place.
How we write
Three rules keep the writing honest:
- No fluff, no listicles, no filler. Nothing here is AI-generated padding written to rank for a keyword. If a post is long, it's because the problem was.
- Real, copy-ready code. Every snippet came from a build that ran. The line that matters is highlighted, not buried.
- Opinions, with reasons. We'll tell you what we actually reach for and why — including when the popular choice is the wrong one.
Who's behind this
brokeinprod is published by FLMOR Media, LLC, a Texas limited liability company. It's written by a developer building real applications and writing down the problems worth remembering.
Stay in touch
The best way to follow along is the newsletter — new field notes land there first. You can also find brokeinprod on X, Dev.to, and Hashnode.
Got a correction, a war story of your own, or a question about how a fix was found? Reach us at hello@brokeinprod.dev or through our contact page. Corrections especially are welcome — getting it right matters more than looking right.