You are comparing a downside of an approach with the upside of another. You can just as well do the opposite: when adding a new feature/fixing a bug in a featur

You are comparing a downside of an approach with the upside of another. You can just as well do the opposite: when adding a new feature/fixing a bug in a feature, when using mainstream existing programming styles you need to touch many code units that also play a role in other features. Behavioral Programming seeks to organize the code by features. It is somewhat similar to the expression problem[1], which is also about maintainability in the face of different kinds of changes. Some would be easier in one approach and harder in the other, and some would be the opposite. Without any real data, you cannot possibly determine which of those would be preferable in the "common case", as you don't know what the common case is. In this case the question is, which is more common, a change that affects few code units but many features (win for mainstream styles) or a change that affects many code points but a few features (win for behavioral programming)? [1]: https://en.wikipedia.org/wiki/Expression_problem https://en.wikipedia.org/wiki/Expression_problem