Newsletter: Feature flag mistakes to avoid #10302
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
As is tradition, I only have title-y type feedback. I think it's a bit dry - can we try something like 'Feature flag mistakes we've made at PostHog' (and how you can avoid them) or 'Non-obvious feature flag mistakes to avoid'? Not super helpful, but the first one 'not using them' just feels a classic clickbaity/listicle item. But I don't have something helpful to suggest to improve this so maybe it's fine! |
|
The option "Feature flag mistakes to avoid" was the highest voted option in a newsletter poll we ran FYI. |
There was a problem hiding this comment.
This is tight and very actionable. Additional high-level thoughts:
-
I think, in the intro, we need to connect using feature flags with our broader theme of product engineering. You kind of touch on it, but it should be super explicit that mastering feature flags is a key skill in becoming a good product engineer. I think you could probably start there – i.e. "We're always banging about how product engineers need to XYZ XYZ and feature flags are a key too."
-
Agree with Charles the headline. I view the polls as more topic testing than headline testing. We don't need to go crazy here, but it could do with a little something extra.
|
|
||
| The core of a feature flag's value to developers is the ability to turn them off. They need to be ready for this at any point, which isn't always the case. | ||
|
|
||
|  |
There was a problem hiding this comment.
I think this would be a good one to turn into a Maxhog meme – I'm sure Lottie could dress Max in the pikachu costume! We could use this as the main image.
Co-authored-by: Bijan Boustani <[email protected]>
|
ok, title and intro updated |
Changes
Draft of a feature flag mistakes to avoid newsletter. Would love feedback on:
Checklist
Article checklist