Re:We cut our CI pipeline execution time in half
by chrisandchris on Friday February 17, 2023 @02:03PM
(#34838861)
I can only image how clean code looks & works that is full of feature flags. Glad that I don't need to do that to often :)
Re:We cut our CI pipeline execution time in half
by tempest_ on Friday February 17, 2023 @03:25PM
(#34840059)
They keep adding them until they need an internal library to manage their collection of feature flags.
Then after a while they graduate to feature flags as a service (of which there are a bunch of cloud services trying to have a go at)
Re:We cut our CI pipeline execution time in half
by mariosisters on Friday February 17, 2023 @05:21PM
(#34841417)
The right approach is to immediately remove the flags after rollout…
The actual approach is to maintain a million fucking feature flags, ensuring that almost all possible combinations are essentially untested… better hope you did a good job separating concerns!
Actually, if you work with SMBs/enterprises, I agree with you on customer facing changes. In my past life we would ship very frequently (often more than once a day) but always had to feature flag changes that large clients might see or be affected by. Even something as simple as tweaking the layout of a core flow could cause support headaches and angry customers — customers worth 10s of thousands of dollars per month. Is it worth losing a customer to CD a new button placement?