Oliver Davies
5eba6de81a
This is a follow-up to commit 3be9031de8
as each daily email has a `permalink` value that overrides the default
content type permalink.
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
---
|
|
title: You should know when to remove a feature flag
|
|
date: 2024-03-12
|
|
permalink: daily/2024/03/12/you-should-know-when-to-remove-a-feature-flag
|
|
tags:
|
|
- software-development
|
|
- feature-flags
|
|
cta: subscription
|
|
snippet: |
|
|
Yesterday, I said feature flags should be short-lived. But how do you know when a flag can be removed?
|
|
---
|
|
|
|
[In yesterday's email][yesterday], I mentioned my recent ["minimum viable feature flag" tweet][tweet] and that I think feature flags should be short-lived.
|
|
|
|
But how do you know when a feature flag should be removed?
|
|
|
|
My approach is to add a TODO comment above where I use a feature flag.
|
|
|
|
In that comment, I added why the feature flag was added and when it can be removed.
|
|
|
|
It can be something like "Remove this when x is deployed" and/or a targeted date when I'd expect to be able to remove the flag.
|
|
|
|
Then, when reading through the code, anyone can see when it should be possible to remove each feature flag, and it's easy to find flags that can be removed by reviewing the TODO comments.
|
|
|
|
[tweet]: https://twitter.com/opdavies/status/1767846980250714261
|
|
[yesterday]: {{site.url}}/archive/2024/03/11/feature-flags-should-be-short-lived
|