2 ms·
Right, basically this. If you're shipping something new that could affect production, put it behind a feature flag so the code paths that are already live are u
by shawnps 5y ago
Right, basically this. If you're shipping something new that could affect production, put it behind a feature flag so the code paths that are already live are unaffected. Continuously ship small changesets so that it's easy to roll back if necessary.
- dpark 5y ago> If you're shipping something new that could affect production… Which, again, is everything. I’m all for feature flags, but they cover very specific cases. There are many changes that feature flags cannot cover. The addition of the feature flags itself can introduce bugs. They are a great feature but only one small piece of protecting production.