Show HN: Dorkly: Open Source Feature Flags

Re:Show HN: Dorkly: Open Source Feature Flags by hinkley on Thursday June 27, 2024 @10:05PM (#40817096)

But it’s also common to stick those flags back under some sort of audit system so we know why and how weird states got set. The simplest way is a separate repo with simpler rules for pushing to master.

Though you could also create your own audit system (just make sure it functions even when the entire site is down)

[ Parent | on HN ]

Re:Show HN: Dorkly: Open Source Feature Flags by bottd on Thursday June 27, 2024 @10:45PM (#40817264)

This is all decided by business needs, not by engineer preference. If devs aren’t pulling the levers it is good to expose them in an accessible interface, not plaintext.

[ Parent | on HN ]

Re:Show HN: Dorkly: Open Source Feature Flags by hinkley on Friday June 28, 2024 @02:24AM (#40818243)

Let’s not pretend like these “business needs” don’t often boil down to a couple of tropes and that the story doesn’t change after a couple of post mortems are turned in for perfectly predictable failure modes.

[ Parent | on HN ]