Hardcoding Feature Flags is Preferable to Using Management Software

Critique of Feature Flag Management Software

Feature flag management software, while marketed as powerful, introduces significant complexity and risk into product development. The marketing often overstates the necessity for scaling to thousands of flags and making runtime changes without deployments, restarts, or reviews.

Architecturally, these systems are described as glorified if statements managed in separate processes, requiring their own infrastructure, hosting, and monitoring. This adds more moving parts to a software system, increasing potential points of failure and maintenance overhead.

Development and Security Concerns

From a development perspective, feature flag management software can lead to non-deterministic behavior, making code harder to reason about. Long-lived flags, even with good intentions, contribute to technical debt that can ossify the codebase. This risk exists with hardcoded flags but is more visible and manageable.

Security-wise, these systems increase the attack surface and potential vulnerabilities. Adding more components to a software system necessitates scrutiny to determine if the benefits outweigh the introduced risks.

Advantages of Hardcoded Feature Flags

Hardcoded feature flags address many of the issues associated with management software by offering a simpler, more reliable, and safer approach. This method is considered the most straightforward way to implement feature toggles.

Implementation can involve a simple JSON file read at application startup to control feature visibility. The key is to actively manage these flags, removing them when no longer needed or integrating them as actual behavior if they persist too long, using standard development processes for changes.