Nice one! We currently use the same system and it allows us to be way more flexible and handle any deployment easily as anything can be release anytime.
The only down side to this is that some versioned components can get quite beefy so you need to keep up with cleaning any previous versions not in use anymore.
Thanks! Yes, cleaning old flags can be a pain. One have to be diligent and not let old code hang for too long. Having “Remove feature flag” as last todo in your task helps. How do you solve that?
We create a tech debt list that we continuously work every sprint. In general, once we enable a feature flag we wait at least 1 week to start working on removing the previous version. Just in case a big problem arise with the new one.
We always have someone in the team doing support for a sprint and we rotate, so that person usually works on the removal of the flag and other non heavy tasks.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice one! We currently use the same system and it allows us to be way more flexible and handle any deployment easily as anything can be release anytime.
The only down side to this is that some versioned components can get quite beefy so you need to keep up with cleaning any previous versions not in use anymore.
Thanks! Yes, cleaning old flags can be a pain. One have to be diligent and not let old code hang for too long. Having “Remove feature flag” as last todo in your task helps. How do you solve that?
We create a tech debt list that we continuously work every sprint. In general, once we enable a feature flag we wait at least 1 week to start working on removing the previous version. Just in case a big problem arise with the new one.
We always have someone in the team doing support for a sprint and we rotate, so that person usually works on the removal of the flag and other non heavy tasks.