What is the limit of N maximum methods that you allow in your classes?

Question

When filling out an Overview of Object Oriented Concepts (To provide some research scientists with real data on software development), I came across this question:

What is the limit of N maximum methods that you allow in your classes?

A survey is then performed if you reorganize your classes as soon as you reach this limit.

I honestly never thought of such a restriction when developing my applications and wondered what argument was. Why do I want to impose on myself an arbitrary number, which probably depends heavily on the functionality of the classes?

Answer 1

N . " ". all-can-do-whatever-it-is.

, N, . .

Answer 2

, , , .

, 20 , , SRP > .

Answer 3

, , , - 10-20 , , . J2EE, Enterprise Java Melons.

. , , .

Answer 4

, , .

, 30 , 3 (Umm, 30 , - , kloc)

/ -.

- ​​ - , 4 5 .

, JDK- , , , , 20.

Answer 5

, , - , " !" , , do-all, .

If I open the source file, which I have not looked at before, and see more than 10-20 methods, I will probably scan it to see if it can somehow be reinstalled.