Comment on Principles for building and scaling feature flag systemsComments−adasdasdas2yMore principles- Require in code defaults for fault tolerance- Start annoying the flag author to delete if the flag is over a month old- Partial rollout should be by hash on user id- Contextual flag features should always be supplied by client (e.g. only show in LA, the location should be provided by client)−hamandcheese2yPartial rollout should be by hash on user idWith a per-flag salt as well, otherwise the same user will always have bad luck and be subject to experiments first.−zellyn2yOur in-house solution hashes flagname+key, and LD does the same but adds salt−stravant2yBetter yet require always the same default for boolean flags, so that it's easier to reason about lifecycle for them.−tantalor2yStart annoying the flag author to delete if the flag is over a month oldNo problem, filter that email directly to spam folder.
Comments
More principles
- Require in code defaults for fault tolerance
- Start annoying the flag author to delete if the flag is over a month old
- Partial rollout should be by hash on user id
- Contextual flag features should always be supplied by client (e.g. only show in LA, the location should be provided by client)
With a per-flag salt as well, otherwise the same user will always have bad luck and be subject to experiments first.
Our in-house solution hashes flagname+key, and LD does the same but adds salt
Better yet require always the same default for boolean flags, so that it's easier to reason about lifecycle for them.
No problem, filter that email directly to spam folder.