Quick deploy is great until it isn't

Auto-deploy on push is one of the nicest things about modern hosting. Commit, push, and the site updates before you've switched tabs. It also means every push to main is a production release, whether you meant it that way or not.

So I changed how I treat main. Small commits, no half-finished work, and if a change includes a migration I run it right after the push instead of assuming the pipeline will. Convenience removes steps, but it doesn't remove consequences.

The cheapest safety net is boring: a backup first, a quick check afterwards. Fast deploys are only fast if you never have to spend the afternoon undoing one.