Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

I think this is the only fully correct answer here, although Oded more or less states the same thing. You can aim for method and file lengths but the primary considerations need to be stated first. You can't avoid implementing the necessary logic and that is the strongest determinant of the length of methods, and consequently modules. You may not find an avenue or reason to break up a class as it grows due to new requirements. You might see an artificial way to do it that increases the complexity but that would be counter productive, indicating why this is the correct answer.

NeilG
– NeilG

2023-11-13 06:44:45 +00:00
Commented Nov 13, 2023 at 6:44

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »