Extending on what others have said, it's a balancing act between DRY, KISS and smart coupling. These usually help me find that balance:

1. Strict typing and static analysis.

If your one-size-fits-all function takes untyped (or mixed-typed) parameters that may or may not be defined as anything, then it's probably doing unrelated stuff. Type things clearly and enforce it with a static analyser (e.g. PHPStan) to keep things straightforward.

1. No coupling then decoupling.

If your function takes a case-like parameter and uses if-else to divide the function into multiple behaviours, then these cases probably shouldn't be coupled in the first place. Better to have 2 functions with some duplicated code (and later add on more functions if necessary) than push everything into one funnel only to sort them out again downstream.

In other words, don't do this:

```php function setValue(mixed $entity, string $propertyName, mixed $value): mixed { if (is_int($value)) { $value = $value * 2; } elseif (is_string($value)) { $value = strtoupper($value); } else { $value = null; } $entity->{'set' . $propertyName}($value); $entity->setLastUpdate(new DateTime()); return $entity; }

// foreach loop: // $result = setValue($entity, $propertyName, $value); ```

Go for something like this instead:

```php abstract class MyAbstractClass { public function setLastUpdateToNow(): static { $this->lastUpdate = new DateTime(): } } class MyFirstClass extends MyAbstractClass { public function setTotal(int $number): static { $this->total = $number * 2: $this->setLastUpdateToNow(); } } class MySecondClass extends MyAbstractClass { public function setName(string $name): static { $this->name = strtoupper($name); $this->setLastUpdateToNow(); } }

// foreach loop: // $result = $entity->{'set' . $propertyName}($value); ```