Hacker News new | ask | show | jobs
by cloudrkt 1895 days ago
Deploy on a friday is still a no go for us.
2 comments

It's often required that we go on a Friday or Saturday to minimize potential impact if there's an issue
When I was briefly working in a construction plant. Weekends is when non critical or potentially risky operations on machinery would be done, as to not block the production chain during workdays.
When you work on weekends too, a friday is just like any other days.
Some [1] propose to split the week in a different way, so that you take a day off on Wed and one on Sun and you work on Sat, so Fri becomes like Thu.

[1] https://www.youtube.com/watch?v=ALaTm6VzTBw

Or when you have a robust CI process in place
I've yet to see the place that had the level of testing, and infallability of the CI process, to where I wanted to deploy on a Friday. Yeah, it may be a low chance that anything will go wrong, and an equally low chance we'll be unable to easily rollback, but so few things can't wait until Monday that I want to roll those dice.
For any somewhat complex architecture, even with great tests and canaries there will be unexpected issues.
I have 100% code coverage in my unit tests + behavioral tests (with cucumber).

And yet, problems still happen.

Programming is the art of adding bugs to an empty text file.

Even an empty file can contain a bug, by virtue of being empty.