4 ms·

Show HN: RM Flags – Automated feature flag maintenance for your codebase

4 points by bakatz91 3y ago

Hey HN, excited to show my newest product: RM Flags. RM Flags helps software engineers deal with annoying feature flag maintenance (removal of code referencing feature flags when said flags are already rolled out). Check it out and let me know what you think! Thanks

bakatz91 3y ago
P.S. This is also on Product Hunt: https://www.producthunt.com/posts/rm-flags https://www.producthunt.com/posts/rm-flags - grateful for any feedback either here or on PH!
lukevp 3y ago
How do you know if a flag is rolled out or not, once you get to LD integration? What if it’s a flag that’s just not in development yet? Also how long does it have to be 100% before considering it rolled out? I don’t want to lose the ability to disable a failing feature if it’s major for maybe a couple months, but for something small I may be fine removing it in a couple weeks… are you just using the state of the flag not changing as “rolled out”? Lack of targeting? There’s not really much info. What languages are supported? We use feature flags throughout a codebase, not just on the frontend or backend.
- bakatz91 3y ago
  Thanks for the comment! Answering below: 1. At the moment, you'll have to manually type in which feature flags you'd like to remove when you set up the monitoring job. In the future, there will be integrations with popular "feature flag as a service" apps like LaunchDarkly, and they have an API that returns whether or not the flag is rolled out. The idea is to look at the last modified date and if it has been on 100% for a week or more, consider it as "stale" and remove it. 2. Which programming language(s) are you using? The AI model I'm using has been trained on many different code samples and it's generally able to support any programming language. This is similar to how GPT-3.5/4 works. RE: Using throughout the codebase with different programming languages - no problem. That use case is supported as you can specify file extensions to monitor. i.e. if you have one codebase with js, c#, and ts files you can enter all of those as extensions and RM Flags will clean up all references in those files. Let me know if this helps!

4 points by bakatz91 3y ago

bakatz91 3y ago

P.S. This is also on Product Hunt: https://www.producthunt.com/posts/rm-flags https://www.producthunt.com/posts/rm-flags - grateful for any feedback either here or on PH!

lukevp 3y ago

How do you know if a flag is rolled out or not, once you get to LD integration? What if it’s a flag that’s just not in development yet? Also how long does it have to be 100% before considering it rolled out? I don’t want to lose the ability to disable a failing feature if it’s major for maybe a couple months, but for something small I may be fine removing it in a couple weeks… are you just using the state of the flag not changing as “rolled out”? Lack of targeting? There’s not really much info. What languages are supported? We use feature flags throughout a codebase, not just on the frontend or backend.

bakatz91 3y ago
Thanks for the comment! Answering below: 1. At the moment, you'll have to manually type in which feature flags you'd like to remove when you set up the monitoring job. In the future, there will be integrations with popular "feature flag as a service" apps like LaunchDarkly, and they have an API that returns whether or not the flag is rolled out. The idea is to look at the last modified date and if it has been on 100% for a week or more, consider it as "stale" and remove it. 2. Which programming language(s) are you using? The AI model I'm using has been trained on many different code samples and it's generally able to support any programming language. This is similar to how GPT-3.5/4 works. RE: Using throughout the codebase with different programming languages - no problem. That use case is supported as you can specify file extensions to monitor. i.e. if you have one codebase with js, c#, and ts files you can enter all of those as extensions and RM Flags will clean up all references in those files. Let me know if this helps!