[scott_w]

Read any book on the subject, they’ve done the research for you. The Phoenix Project, The State of DevOps Report.

Spend some time in companies that move slow vs fast and you’ll see the difference in their success first hand. You’ll see the metrics on their incidents and severity and customer satisfaction with them.

Oh, and the fact two companies mentioned (Google and Facebook) are two of the most successful companies on earth.

[Scubabear68]

See my comment elsewhere taking “people are the product” out of this conversation.

Facebook and Google and like companies do not care if they piss users off. They churn features constantly, break people’s flows on a regular basis, A-B test features so different people get different experiences.

They get away with this because the “users” aren’t users, they and their data are the product. You pay nothing to use their services, and you get what you pay for.

[scott_w]

Good thing my argument didn’t hinge on them, then. Mind picking up on anything else?

[Scubabear68]

You used them as exemplars.

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).

[scott_w]

Read above: Accelerate and The State of DevOps are two reads.

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.

[Scubabear68]

Assuming an 8 hour day, that’s a deployment every 24 minutes, and that’s not good enough?

Why in Earth wouldn’t you coordinate releases? Seems like utter chaos.

[igetspam]

Have you taken the time to read any of the reference material? Have you looked at any of the actual data? Are you aware of how CD with trunk based development works?

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.

[scott_w]

Where is your data to backup your assertion that it’s “chaos?” What research can you cite in opposition to the information I’ve provided?

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.

[deely3]

Look, you not convincing at all.

1. Should I skip books that do not confirm your point of view?

2. What if I already spent time in these companies and found no big difference?

3. So, why companies that use different approach still exists and even (mamma-mia) profitable?