Can you point out specifically where someone says releasing up to 20x a day into production for a paid platform is a good thing?
I am not talking about the capability. I grant being able to release quickly and often is desirable. I question the wisdom of actually releasing multiple times a day into production as a best practice. In my mind it is highly inefficient and offers too much churn for users (eg exactly my experience with Facebook, a chaotic broken product that changes hourly and makes people feel like the product t is gas lighting them).
From experience, across teams, we deploy probably 20x a day and we're actively trying to deploy more often. Our customer NPS scores are pretty high and our change failure rate is low. We're also a very successful B2B SaaS.
Why in Earth wouldn’t you coordinate releases? Seems like utter chaos.
You're making assertions that imply you haven't considered anything but your own bias. Your question only works if you have no understanding of how these things actual function
The goal is to reduce the amount of time it takes for a change to land in production. Your eight hour work day implies you have developers only in a single location too, instead of the distributed work force most of us have now.
You seem to be (blissfully?) unaware of how high performing organizations operate.
Where are the customer satisfaction surveys that say deploying to production multiple times a day is making their experience worse? Where are the articles showing deploying more reduces revenue? Where is the link between more deployments and reduced reliability?
We’ve provided our evidence, now put up our shut up.
