I'm assuming this is not an April Fools' joke, and my comments are targeted at the discussion it sparked here anyway. A flat branching model simplify things, a

I'm assuming this is not an April Fools' joke, and my comments are targeted at the discussion it sparked here anyway. A flat branching model simplify things, and the strategy they describe surely enables them to ship features to production faster. But the risks I see there: - who decides when a feature is ready to go to production? The programmer who developed them? The automated tests? - features toggleable by a flag must, at least ideally, be double-tested -- both when turned on and off. Being in a hurry to deploy to production wouldn't help on that; - OK, staging environments aren't in parity with production. But wouldn't they be better than the CD/CI pipeline, or developer's laptop, testing new features in isolation? - Talking about features in isolation: what about bugs caused by spurious interaction between two or more features? No amount of test would find them if they only test features in isolation