One of the premises is that the minimum level of competence of the team should be above average, which is not feasible everywhere. And "The short-lived featur

One of the premises is that the minimum level of competence of the team should be above average, which is not feasible everywhere. And "The short-lived feature branch should only last a day or two and never diverge from the trunk enough so that a merge back is problematic. After the seal of approval from code reviewers and CI daemons, it should be merged back into the trunk. It should be deleted, as proof of convergence. The developer in question may then go ahead and make the next short-lived feature branch for the next story/task they’re doing" https://trunkbaseddevelopment.com/youre-doing-it-wrong/#duration-of-short-lived-feature-branches https://trunkbaseddevelopment.com/youre-doing-it-wrong/#dura...