I think the author read "inadequate" in a different way than it was written. The way I read the tweet is not "then your practices are shit", but rather "then yo

I think the author read "inadequate" in a different way than it was written. The way I read the tweet is not "then your practices are shit", but rather "then your practices are not ready yet". I.e. as an assessment, not judgement. It's a bit of a "you must be this high to ride" situation for Friday deploys. With 64 releases, I don't expect the release pipeline to even be ready for this - we're doing a few releases a day and I'll still choose not to do some of them on Friday afternoon. (Especially dns changes that could bring down everything) Then there's a risk of something going wrong regardless of how well you're prepared. Don't release on Friday is stupid, ignore Fridays is stupid. How about "work on your release processes, so that the scope of what you're comfortable releasing on Fridays grows over time"?