Deploy Friday: A Risk Assessment

The discourse around Friday deployments reveals more about team culture than engineering practice. Let’s examine both sides with the seriousness this topic deserves (moderate).

The Case Against

  • Weekend on-call is involuntary overtime with extra anxiety

  • Rollbacks under pressure are error-prone

  • Your monitoring probably has gaps you haven’t discovered yet

  • "It’s just a small change" is the opening line of most incident reports

The Case For

  • If you can’t deploy on Friday, your deployment process needs work

  • Feature flags exist for a reason

  • Continuous deployment means every day is Friday

  • Artificial deployment windows create batch-size problems

The Verdict

If deploying on Friday feels dangerous, that’s information about your system, not your calendar. Fix the system. Build confidence in your rollback process. Invest in observability.

Then deploy whenever you want. Even Friday.

The tide doesn’t check what day it is. It has confidence in its rollback mechanism.

— JP, from the void.

Reply

Avatar

or to participate

Keep Reading