IMHO it's also down to how your userbase prefers to get updates. Sure, no user wants to use buggy code, but bundling and explaining changes in regular interval could also be better use of their attention span.
There's a separation though between releasing and delivery.
Ideal world in terms of simplicity delivering features as they're ready (continous delivery)
However you can still shipe your code and hide new features with toggles. This means your code is always deploying, so you get all the benefits of feedback loops but you control what the user sees. The downside is feature toggles have a cost in terms of maintainability and effort.
Yeah I think that after a threshold of complexity and size of user base basically every new feature will have to be behind a/b test or feature toogles.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
IMHO it's also down to how your userbase prefers to get updates. Sure, no user wants to use buggy code, but bundling and explaining changes in regular interval could also be better use of their attention span.
There's a separation though between releasing and delivery.
Ideal world in terms of simplicity delivering features as they're ready (continous delivery)
However you can still shipe your code and hide new features with toggles. This means your code is always deploying, so you get all the benefits of feedback loops but you control what the user sees. The downside is feature toggles have a cost in terms of maintainability and effort.
Yeah I think that after a threshold of complexity and size of user base basically every new feature will have to be behind a/b test or feature toogles.