Useful post outlining a lot of common pain points I have experienced myself in my career. One of the reasons I went for an open source solution ( https://featu

Useful post outlining a lot of common pain points I have experienced myself in my career. One of the reasons I went for an open source solution ( https://featurevisor.com https://featurevisor.com ) that's Git based, and every change is done via Pull Requests. Building blocks: - Attributes for conditions: https://featurevisor.com/docs/attributes/ https://featurevisor.com/docs/attributes/ - Segments for targeting users: https://featurevisor.com/docs/segments/ https://featurevisor.com/docs/segments/ - Features with variations and rules: https://featurevisor.com/docs/features/ https://featurevisor.com/docs/features/ Process: - Merge PRs - Trigger CI/CD pipeline: https://featurevisor.com/docs/deployment/ https://featurevisor.com/docs/deployment/ - Consume with SDK: https://featurevisor.com/docs/sdks/ https://featurevisor.com/docs/sdks/ Use cases: - User entitlements: https://featurevisor.com/docs/use-cases/entitlements/ https://featurevisor.com/docs/use-cases/entitlements/ - Testing in production: https://featurevisor.com/docs/use-cases/testing-in-production/ https://featurevisor.com/docs/use-cases/testing-in-productio... - A/B testing & experimentation: https://featurevisor.com/docs/use-cases/experiments/ https://featurevisor.com/docs/use-cases/experiments/ - Remote configuration: https://featurevisor.com/docs/use-cases/remote-configuration/ https://featurevisor.com/docs/use-cases/remote-configuration... You can also generate types as a package for compile-time safety: - Code generation: https://featurevisor.com/docs/code-generation/ https://featurevisor.com/docs/code-generation/ The post and the comments here give me more ideas on how to improve it with more features now.