git co master
git co my-branch -- .
git add -up . # select changes relevant to first pr
git commit
git reset HEAD --hard
# and again...e.g. first pass adds a new screen and just dumps the output
second pass adds input fields and controls
next pass adds validation
then add animations
etc
1. Frequently old code needs to be touched or refactored. Feature flag would not be enough.
2. Even feature flag itself can be a risky addition, and might affect existing customer usage.
Most of the time old code does need to be touched, there really aren't those perfect new isolated features, at least in my experience.
For example, I'm not approving anything without input validation (frontend or backend). I have no idea if you're actually going to add validation later before the fflag is removed. "Trust me bro" doesn't work for me.
Feature flags don’t mean throwing the baby out with the bathwater.
Kind of.
Atomic commits are hard.
The original post describing it: https://martinfowler.com/bliki/StranglerFigApplication.html