Ship Faster; Avoid Dragons with Feature Flags
We've all found dragons during a deployment. Whether your're a developer, a DevOps engineer, an SRE, or a PM, you've all got a common goal - hoping that the next change doesn't unleash a dragon on Production and keep you up for the next 5 hours restoring your environment. But what if you could use the practice of feature flagging as a shield? Breaking your code into feature flags lets you create defensible positions that are fire (aka failure) resistant by giving you the ability to immediately turn off a problem release. It's like being able to tiptoe out of the cave before the dragon wakes up. In this session, you'll learn about the practice of using feature flags, how they can be implemented, and ways you can use them to tame those dragons and protect your party from danger. We'll explore uses for developers, Product Managers, SREs and much more and get you to a place where you can ship faster, and avoid charring with Feature Flags.
None needed, i'm here to teach from the ground floor!
- Feature flags give you a defensive tool to ship faster, but protect yourself from dragon-fire
- You can use them for rollouts, killswitches, environment control and more
- They are more than just frontend. Backend users can apply too, as well as DevOps/SRE/PM teams