Our goal in this first project together was to streamline access to the full power of feature flags when building and releasing code with Azure DevOps.
As with any type of process, the more work and people involved, the harder it becomes to consistently deliver quality results on time. The same …
If our organizations want to survive this period of political and economic uncertainty, they must be able to move with speed and adaptability.
Teams working with feature flags usually come to the conclusion that a large number of active flags isn’t necessarily a good thing. While each active feature flag in your system delivers some benefit, each flag also comes with a cost. I’m going to explain those costs, such as cognitive load and technical debt, and explain how to avoid them.
Feature flagging systems can sometimes become victims of their own success. The benefits of feature flagging along with the broad applicability of the technique can lead to rapid adoption within an organization, and pretty soon the number of active flags can start to feel overwhelming. One way to keep your feature flags manageable is to introduce a categorization system.