From 8135cb35e0b8d46bb1e95c99a2c6387eea64eba3 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 13 Mar 2024 23:43:20 +0000 Subject: [PATCH] Add daily email for 2024-03-12 You should know when to remove a feature flag --- source/_daily_emails/2024-03-12.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 source/_daily_emails/2024-03-12.md diff --git a/source/_daily_emails/2024-03-12.md b/source/_daily_emails/2024-03-12.md new file mode 100644 index 000000000..dbf8ea7d8 --- /dev/null +++ b/source/_daily_emails/2024-03-12.md @@ -0,0 +1,26 @@ +--- +title: You should know when to remove a feature flag +date: 2024-03-12 +permalink: archive/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