Intentional Deployment: Best Practices for Feature Flag Management

[@GrantM1337]

This was exactly what I needed. Thank you!

[@alextaylor2551]

Wow- I’m surprised no one is watching this- good presentation thanks!

[@ankushpandit]

They are waiting to be another example :)

[@thinhtat]

i'm thinking :) . thanks for presentation, it helps me a lots

[@ArjunVerma-lq4cf]

Nice and imp video to watch before starting feature flag use

[@leeworrell3761]

This video really answered my questions. Thanks so much. Great video.

[@ornous]

Great talk!

[@yp5387]

Do not release if you can't rollback it in 5 minutes..

[@privacyvalued4134]

Way too complicated. Just roll code out to everyone. If it breaks, then roll it back and do a postmortem. The Knight Capital Group lost their business because they used feature flags NOT because they managed them poorly. If anything, it's an excellent example of why to NOT use feature flags in the first place. Your code is in version control, so it's easy enough to rollout and back again. Use a test suite against features to prevent breakage and roll out changes on set days of the week and a set time of day such that there is sufficient staff on hand to deal with actual breakage (i.e. don't deploy on weekends or at 3 am when no one is in the office let alone conscious). If your code or setup is too complicated to just rollout, then your code is written incorrectly and/or your infrastructure is poorly designed and you should be looking at those things rather than feature flags as a solution.