←back to thread

232 points ksajadi | 1 comments | | HN request time: 0.213s | source
Show context
bigmattystyles ◴[] No.45140579[source]
Broke the read-only Friday rule…
replies(2): >>45140943 #>>45141386 #
jkingsman ◴[] No.45140943[source]
I know this is a tongue in cheek casual comment, but this article is a really good and important counterpoint: https://charity.wtf/2019/05/01/friday-deploy-freezes-are-exa...
replies(10): >>45140998 #>>45141312 #>>45141402 #>>45141439 #>>45141454 #>>45141628 #>>45141856 #>>45142250 #>>45142827 #>>45147202 #
1. jjice ◴[] No.45141856[source]
Not to jump on your comment (since there have been quite a few other replies already) but just to add another personal anecdote: having been on the more senior end of a junior merge/deploy gone wrong and losing a Friday night or a weekend ping, I'm okay with an additional empty day throughout the week.

I've found that little things like that breed a growing resentment and stress that compounds, until someone wants to leave the company. Thursday night outage that I have to hop on? Much smaller deal than a weekend where I have established plans.

One can argue "why was the PR approved in the first place", but sometimes people make mistakes. It especially sucks when there are limited people that know how to troubleshoot and resolve the production issues with a system, even more so when the on-call individual may have not even reviewed the code initially.

All that said - I'd love to deploy as normal on Fridays! I've just found that the type of businesses I've worked at can wait until Monday, and that makes our weekends less risky.