large-file-control

To decide whether to inline or extract code, evaluate the file size and responsibility boundaries. You should extract code into a new, focused module when the current class becomes too large and mixed responsibilities begin hurting code readability and maintainability.

Mixed responsibility occurs when a single large file or complex module handles multiple unrelated tasks. This code sprawl reduces clarity and makes maintenance difficult, requiring you to split the logic into separate, focused classes to restore single-responsility design.

You should refactor a large class to prevent code sprawl before implementing a new feature if the module is already complex. Evaluating the file size management criteria helps determine whether to keep new logic inlined or extract it into a separate class.

Yes, this approach works for managing code size in any complex module, class, or method where readability and maintainability are critical. It provides general criteria for preventing file sprawl without depending on specific platforms or frameworks.

The best way to maintain code readability when adding new methods is to assess whether the logic fits the existing module's responsibility. If adding the method causes file size bloat or mixed responsibility, extract it into a new, focused class instead of inlining.