"The one that makes sense"

Patterns and principles are guidelines, not rules. You don't want to just apply them blindly.

You need to balance principles. Over-applying the DRY principle can lead to more complex logic that's harder to understand than if you just wrote code in-line.

The rule I see is functions should be fairly atomic and almost obvious what they do in context of the code.

At least for my small brain that's how I like it. I can understand some complex abstractions but rembering that actually this function behaves in three different ways depending on what flag is set is awful. It means you could look at one example and be totally wrong in another. Ideally you could guess the functions purpose even in a black box setting based on inputs outputs and the name should then make it obvious.