Blog
Notes on feature flags, A/B testing, and keeping experiments in the repo. Concrete, and mostly about files.
- A/B testing for developers: experiments in code A/B testing for developers means running experiments in code, not a dashboard: split traffic deterministically, measure one metric, and conclude with a decision.
- dif vs GrowthBook: flags in your repo, or in an app dif vs GrowthBook: both are open source. dif keeps flags and experiments in your repo as files; GrowthBook runs them in a warehouse-native app. How to choose.
- Feature flags in git: the case for flags as code Feature flags in git means flags live as code in your repo, reviewed in a pull request and versioned like anything else. Here is how the workflow works and its tradeoff.
- The open-source LaunchDarkly alternative: feature flags in your repo The open-source LaunchDarkly alternative: feature flags and A/B tests as Markdown files in your repo. MIT licensed, no per-seat fees, one command to install.
- What are feature flags? A developer's guide A feature flag is a runtime switch that turns a feature on or off without a deploy. Here is how feature flags work, the main types, and how to keep them from rotting.