Why we ship on Fridays (and what we do differently to make it safe)
The 'no Friday deploys' rule is a symptom, not a discipline. The real fix is a deploy pipeline you trust on any day of the week — including the one before the weekend.
The Friday taboo
'Don't deploy on Fridays' is a rule that protects you from your own pipeline. If you can't trust the deploy enough to ship on Friday afternoon, you can't trust it on Monday morning either — you've just narrowed the window where the bug shows up.
What makes Friday deploys safe
Feature flags. Trunk-based development. Canary rollouts. A rollback you've practiced. Tests that catch regressions before merge, not after. Monitoring you trust enough to page you when something's wrong.
What we still don't ship on Friday
Database migrations. Anything that's hard to roll back. Big platform changes. The taboo is right about a small set of high-blast-radius changes — and wrong about the everyday work.
Ship on Friday. Or don't. But fix the pipeline first.
