5 ms·
I couldn't work out what this does. A library for mapping booleans to and from strings?
by rwmj 6y ago
I couldn't work out what this does. A library for mapping booleans to and from strings?
- dabeeeenster 6y agoHi - we're a feature flagging platform. You can put new features that you are working on behind boolean flags and then manage those features from our dashboard.
- rwmj 6y agoStill unclear! "Feature" means a software feature? For example "I've implemented the feature of sorting customer records by date of birth"? I don't really understand why anyone would need a service to manage software features, so maybe feature means something else.
- dabeeeenster 6y agoWe have an overview of why you might like to use a feature flagging platform here: https://docs.bullet-train.io/overview https://docs.bullet-train.io/overview Hopefully that helps!
- kristopolous 6y agoThis sounds like it could easily and quickly lead to really poor bug reproducibility, documentation, and discovery especially if the issue is in action-at-a-distance anti-patterns. Am I just being a curmudgeon or is this a reality? I'll happily accept a "no you're crazy".
- tashoecraft 6y agoThis is used extensively. X customer wants to test y feature, but z customer is the middle of a large test and refuses to see c feature. Roll out feature to test client, slowly roll out feature to each client. Something to wrong? It’s incredibly fast to update the flags.
- camnora 6y agoFor smaller projects and teams, something like feature flagging can probably be avoided unless A/B testing is required. For a company that has hundreds of engineers, with daily continuous deployment, it helps to have certain in-development features gated behind flags. When it comes time to deploy these new features, they can gradually be rolled out to users. If the feature starts triggering exceptions, it's very easy to scale back. Once the beta feature becomes stable, often the feature is removed (along with all logic in the source code guarding this feature). Similarly, for A/B testing, the feature flagging and logic is removed once a test is deemed to have either passed or failed the A/B experiment. Like anything else in software, feature flagging can incur technical debt if not properly maintained.
- deleted 6y ago[deleted]
- dmitriid 6y agoFeature flags are used for gradual rollout and testing of features. Including, but not limited by, A/B tests, region-locking features, rolling to features to internal users only and so on. For example, you're developing a new version of the checkout page for your company from scratch (it can be a store selling physical goods, or a subscription service, or anything that requires payment). It means that for a while it will not have feature parity with your existing checkout page. So first you implement feature parity with, say, German payment options (credit cards and Sofort). Then you set up a feature flag saying "for 5% of German customers display the new checkout", and monitor it. Then you bump it up to 10%, then to 50%. Meanwhile you're working on accepting payments via Swish in the new checkout in Sweden. Once it's ready, you add a feature flag saying "for 5% Swedish customers display the new checkout" (and in parallel, you're probably already displaying the new checkout to 50% German customers). And so on. In their core feature flags are not really more than a glorified if statement, but: - you want to view them, and handle them in a single place so that you can adjust the various parameters or quickly shut down a feature if it misbehaves - this single place has to be scalable enough that it survives an influx of customers potentially triggering dozens of feature flags across your software
- brunoluiz 6y agoIs a service for feature flags, where feature flags are a software pattern in a way. If you want to learn more about it, have a look into this: https://martinfowler.com/articles/feature-toggles.html https://martinfowler.com/articles/feature-toggles.html In a nutshell, it allows developers to deploy new features but hide them based on a flag. Once it is ready to be released (example: product gave an ok, big announcement happened etc), then this feature just needs to be enabled through this flag. Now, this flag can be an environment variable, but for apps you will probably need a service, which the app always fetch the latest feature configs. We use it here (although using Flaggio https://github.com/victorkt/flaggio https://github.com/victorkt/flaggio) and it is super useful for continuous delivery. And you can as well control features based on groups (example: show just for beta users) or hide features if some bug was discovered.
- marcus_holmes 6y agoI'm always curious about Feature Flags - I'd love to use them. But they only seem to work if the interface doesn't change. From the example you gave: function reticulateSplines(){ if( featureIsEnabled("use-new-SR-algorithm") ){ return enhancedSplineReticulation(); }else{ return oldFashionedSplineReticulation(); } } All well and good as long as the enhancedSplineReticulation returns the exact same structure that the old one did. If it doesn't, then a bunch of code that handles the new reticulated splines also needs to be behind a flag (because the structure changed). And that could mean a chunk of UI needs to be duplicated behind a flag because it changed, and so on. How do you use feature flags when the features aren't just trivial changes to methodology, but affect multiple parts of the system?
- markn951 6y agoCheck the flags in multiple parts of the system, or duplicate some logic and have two completely self-contained components, one with the new pieces and one untouched.
- marcus_holmes 6y ago
- funkaster 6y agofeature flagging allows you to separate code deployment from feature releases. It’s a change in dev methodology/mentally and usually goes hand-in-hand with “trunk-based development” (trunk/master is always stable and you should avoid long lived branches). a good feature flag service should also allow you to do % rollout to try to de-risk the release of a new feature, some times even auto-closing the feature if some specific metric passes a certain threshold (e.g. dau dropped 10%, number of errors increased x%, etc)