On February 3rd at 1 PM ET, we’ll host the Flagsmith team on our React Wednesday show to discuss why application development and delivery are better with Feature-flag-driven development.
What are Feature Flags and Why Should I Care?
A decade ago, I led a large technical team for an enterprise-sized education provider based in the United States. Our schedule involved releasing code every two weeks. The technology leadership of this organization took a very dim view of off-cycle production changes. Each change needed to be scheduled weeks in advance, with no room for mistakes. If an issue made it to production, the technical team was in hot water with leadership.
To avoid rough meetings with the CTO, we created a homegrown feature flag system whereby we could release code to production and selectively enable features as we liked. Should there be an issue with a released feature, we’d simply turn it off in our feature flag system. As you might imagine, our post-release stress dropped considerably.
Feature flags offer more than just executive conflict avoidance. You can selectively enable features for development environments, user segments, geographies, or even stage rollouts to your liking.
What is Flagsmith?
Flagsmith is an open-source solution for defining and managing server-side and client-side feature flags across many different programming languages. Flagsmith contains SDKs for common platforms, a server-side REST API, and a web user interface for flag management.
You can download and self-host Flagsmith in your environment. You can also have the Flagsmith team host for you under a SaaS-style arrangement with modest pricing.
Good. We do too. Add your questions about feature flags and Flagsmith in the comments of this blog post. We’ll ask the questions live on the air with the Flagsmith team.