3 ms·
It could have been intended to be reviewed internally but then somehow was made public by mistake in the insider builds. Where I work we write a lot of experim
by tuwtuwtuwtuw 5y ago
It could have been intended to be reviewed internally but then somehow was made public by mistake in the insider builds.
Where I work we write a lot of experimental features, behind feature flags which never end up being made available to customers.
Could of course be that they are just making it up. If this was an actual mistake it sounds like their QA is messed up.
- bluefirebrand 5y agoI have been vocal against use of feature flags at my workplace, partly because of the risk of accidentally putting a feature live in a production or other client-facing environment. Just this morning I got to ask "Why is this feature flag enabled in prod" to the stunned faces of people who had insisted that would never happen. Maybe the same thing played out at Microsoft here.