[jaysinn_420]

A company based on doing deploys doesn't seem to understand that the goal should be de-risking the deploys, not de-risking your weekends?

Charity Majors explains it better than I ever could. https://charity.wtf/2019/10/28/deploys-its-not-actually-abou...

[JohnFen]

You can't "derisk" deploys, you can only reduce the amount of risk they incur. Not deploying the day before a nonwork day remains solid advice.

[jaysinn_420]

Sure, you can't remove all risk, but you can reduce it and reduce the risk of unexpected firefighting work. You can implement rolling or blue/green deployments that roll-back on failure. The key is being able to identify failures, which means having meaningful canaries to identify issues. Those canaries can also improve your operational awareness so they aren't just a deployment investment.

If you don't deploy on Friday then you lose 20% of your deploy opportunity. If you only deploy once or twice a week, then sure - choose Monday/Wednesday or something, but if you deploy more frequently then improve your deployment safety.

[bananapub]

> You can't "derisk" deploys, you can only reduce the amount of risk they incur.

to your mind, what is the definition of the word "de-risk"?

[JohnFen]

Reducing the risk of a deployment that catches fire.

[hooverd]

Remove the risk.

[jitl]

Your response sounds like “you can’t derisk deploys, you can only derisk deploys”

[JohnFen]

I was unclear, or perhaps I misunderstood the comment I was replying to. I read it as "deploying on Fridays isn't a problem if you derisk the deploys".

My response was that you can't derisk deploys to the extent that Friday deployments are good practice.

[jitl]

Maybe you can’t derisk deploys on Friday, but we’ve derisked them just fine, and are eager to deploy more frequently Friday and every other day or the week - right now we do once per day, looking forward to continuous delivery to production.