liveBook · Manning

Feature flag

As explained in Think Like a Software Engineering Manager

A feature flag is a runtime control that enables or disables a software feature without requiring a new release.

A feature flag is a runtime switch that enables or disables a feature without requiring a new release. Teams use flags to control production behavior, such as showing or hiding a button. section 12.2.4

Feature flags support several deployment responsibilities:

  • Reduce release risk by enabling gradual launches and disabling features that are not working as intended. section 12.2.4
  • Support experimentation by connecting different feature states with A/B testing and customer-use analysis. section 12.2.4
  • Require regular cleanup: prioritize removing unused flags and include that work in team sprints. section 12.2.4

Gradual feature launch

A team can direct different percentages of users to different feature states, analyze the results, and disable the feature quickly if stability or feedback is poor. section 12.2.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains uses, benefits, A/B testing, and cleanup responsibilities but does not describe implementation mechanics.
Examples
Uses hidden buttons, percentage-based user assignment, customer-use analysis, and emergency feature deactivation.
What you can do after
Operate controlled production launches, experiments, and feature deactivation with lower release risk.
How it connects
Connects feature flags with phased deployment, canary deployment, A/B testing, analytics, and kill switches.

Also explained in

Compare how 8 books explain feature flag →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.