If you're afraid to deploy you're doing something wrong. Deploying is like going to the gym, the more you do it the less it costs you. Tests and E2E integrations can help you to achieve more reliability. I understand that it's hard to risk your Friday, but if you have the habit it will be so easy.
This is definitely true, you do need to have confidence in your tests and policies so that eventually deploying is no big deal. We do continuous deployment, so usually we end up deploying anywhere from 10-15 times a day. Even though 99.9% of the time things go out without a hitch I still prefer not to deploy end of day, especially before I leave. I think it might be more that I feel guilty if something did go wrong and I wasn't immediately available.
I like both answers. I don't deploy last thing during the day or on fridays, but also feel a bit guilty that I don't fix process so that I can.
Also, I will never fully trust computers. I hear so often that a computer does exactly what you tell it to do, what it's programmed to do. But considering the complexity of computers it's often virtually impossible to determine what you've told them to do. So every now and then you tell them to do something that you have to tell them to undo.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.