When implementing feature flags, start small. Run a single feature to see how it works before broadening your scope. #GalaxyConf @saipriya85

Software is not 100% bug-free. Systems are complex and layered. Isolating bugs takes time, rolling back code adds more time to getting stable systems. #GalaxyConf @saipriya85

Apply the lessons you learned using the wrong tool so you don't make the same costly mistakes. @jeremyrcox #GalaxyConf

"Leveraging organizational tools is key to successful organization changes." @calesbrock #GalaxyConf

Collaboration is necessary. These changes wouldn't be possible if QA and Engineering had not worked together. @calesbrock #GalaxyConf

Find one of the biggest problems you have to start testing first. #GalaxyConf

Small interruptions like forgetting to set do not distrub can take up to 22 minutes to recover from #GalaxyConf @InTheCloudDan

What challenges does your team face with release management at scale? -Shifted from bi-weekly to daily release cycle & would have to cope with different levels of quality in production. -Needed to change how we talked about when a feature was live #GalaxyConf @jamesdacosta

We should shift from calling them kill switches to safety nets. You're saving yourself and your customers from a bad experience. @NotKyleSchrade

Kill switch was needed the week before to address a back end issue for new code. The issue was resolved and the code was turned back on. On Black Friday, for retailers this is the biggest day of the year. @NotKyleSchrade #GalaxyConf

You think deploying code on Friday is scary. What about deploying code on Black Friday? @NotKyleSchrade shares how they did just that. #GalaxyConf

When bringing a flag into code, look at how easy it is for anybody to remove. In case people leave the organization. Block commenting can help mitigate risk. #GalaxyConf @launchmarkly

Always be thinking about flag removals. Don't wait until you need to remove a flag, design for removal from the beginning. #GalaxyConf @launchmarkly