3 posts tagged with "naming conventions"

Feature flags (also called feature toggles) let development teams release features safely without redeploying code. They power gradual rollouts, A/B testing, and fast rollbacks when things go wrong.

But as systems grow, feature flags often become a source of hidden complexity. Flags pile up, naming breaks down, and unclear ownership leads to risky changes in production. What starts as a simple toggle system can quickly turn into long-term technical debt.

This guide walks through seven common feature flag mistakes and the best practices to avoid them, so your system stays clean, predictable, and safe to work with.

Can naming feature flags be hard?

Yes. Just like variables in programming, naming feature flags can get tricky if you don't follow a naming standard. When feature flags don't have good names, it can be difficult for people using them to remember what they do.

In this guide, we'll walk through feature flag naming conventions and best practices that help teams manage flags at scale.

"Thank you guys, you rock."​

We love to get emails like the one above. And sometimes we do. 😃 Actually, more often than I've ever dared to imagine.

Part of the reason our users love us (well, when they do) are those million little tweaks we do to our feature flag service on a daily basis.

Normally we don't share those little tweaks and updates