Add Parameters or Create a New Function? Choosing the Right Refactor

Choosing Between Extending a Function and Adding a New One

When a new requirement cannot be satisfied by existing code, developers typically have two structural options: (1) add extra parameter‑based branches to the current function, or (2) create a separate function that implements the new behavior. The trade‑offs involve readability, maintainability, reuse, and backward compatibility.

Adding Parameter Checks

Advantages : Keeps related logic in a single location, avoids duplication, and can be implemented quickly for simple extensions. Default values allow existing callers to remain unchanged.

Disadvantages : Each new condition increases cyclomatic complexity, making the function harder to understand and test. If a default is not provided, all existing call sites must be updated, which may break compatibility.

Creating a New Function

Advantages : Isolates distinct behavior, adheres to the Single‑Responsibility Principle, and improves readability when the new logic differs substantially from the old.

Disadvantages : May duplicate code if the two functions share substantial logic; duplicated code must be maintained in parallel.

Best‑Practice Guidelines

Single‑Responsibility Principle : If added branches cause the function to perform multiple unrelated tasks, split the function.

Extract Shared Logic : Move common code into helper utilities or modules so both the original and new functions can reuse it.

Default Parameters or Overloading : In languages that support them (e.g., Python, Java, C++), define parameters with default values or overload the function signature to introduce new behavior without forcing callers to change.

Design Patterns : Apply patterns such as Strategy or Factory to encapsulate interchangeable algorithms, allowing new behavior to be injected without modifying the core function.

Conclusion

There is no universal rule; the optimal choice depends on the size of the new requirement, the existing codebase, and future extensibility needs. By weighing readability, maintainability, and reuse against the cost of breaking existing callers, developers can select the approach that best fits the project.