Most of the conversation around Cursor focuses on shipping fast with “vibe coding” to quickly ship use facing features which is addicting.

Conversely, there is production support for the products you ship which is time consuming and at times error prone. Conbining the two, one can vibe code admin features which make common production support tasks a breeze. Before AI, I would have never have budgeted calendar time to build these admin features by hand.

Let's keep production support humane: refund a payment with one click as opposed to following a support procedure and manually updating the database; confirming that a location actually matches a pin dropped on a map; reconciling a stuck job; or answering “what happened to this user’s data?” without connecting to a production database and writing SQL by hand.

Why Cursor made the difference

Historically I would have filed that work under “someday,” which actually meant “will never do.” With a capable model, scaffolding CRUD, wiring policies, calling payment APIs, dropping a map component next to a read-only record, and adding an audit log line are all features that now take minutes to implement.

The result has been that I stay almost completely out of the database for day-to-day support.

The takeaway

If you are repeating an administrative task over and over, take the time to build a UI for it. Using AI-assisted development, this can be done in minutes.

For broader context on how Cursor fits into my current stack, see 2026 Dev Tooling.