Bullet Train: Open-source feature flagging

Not to be confused with the Ruby on Rails SaaS template Bullet Train: <a href="https:&#x2F;&#x2F;bullettrain.co&#x2F;" rel="nofollow">https:&#x2F;&#x2F;bullettrain.co&#x2F;</a>

I couldn&#x27;t work out what this does. A library for mapping booleans to and from strings?

If you are interested in this space and don&#x27;t want to purchase a commercial product, check out Flagr [0] which you can deploy and run yourself. It has clients for Go, Python, Ruby and JavaScript. I have only used the basic flagging, but it also supports A&#x2F;B testing as well.<p>No affiliation, just a happy customer.<p>0 - <a href="https:&#x2F;&#x2F;checkr.github.io&#x2F;flagr" rel="nofollow">https:&#x2F;&#x2F;checkr.github.io&#x2F;flagr</a>

I wish there were more examples how to use feature flags. How would you test a feature flag e.g. Halloween discount. As this probably involves both front-end and back-end code. The only way I can think off how this can be tested is by making a special new user with this feature flag.<p>But do you now need to test all possible permutations of the flags combinations? If so, how to determine these permutations? Can imagine you test all possibilities every time??

Had to upvote, been using it for around 6 months, I couldn&#x27;t imagine starting a project without it now.

Why would I use this instead of the feature flagging capabilities provided by Azure for example?

I’m curious, what everyone wants to see in a feature flagging service? privacy? (gdpr, caap) %rollout? flexibility on rules?<p>from my perspective the most important thing would be privacy and ideally no sdk, but I acknowledge that I might be bias...

The example showing &quot;high_spenders&quot; and conditions like &quot;money_spent &gt;= 100&quot;, feels unsettling, and reeks of user-tracking and discrimination.<p>Can we please stop these patterns?