> This is where you end up with functions that take 10 different option parameters, all of which activate a different code path.
Or you could abstract the commonalities out into a higher-order function.
Or you could abstract the commonalities out into a higher-order function.
When they eventually diverge, because they were different operations or structures, so they won't evolve the same... This is where you end up with functions that take 10 different option parameters, all of which activate a different code path. Or structures with completely different fields set depending on where it came from. And guess what? Now you're back to basically one code path or structure per use case, and an extra dependency that didn't exist before and is a nightmare to maintain without breaking one of those existing use cases.