What are the three reasons for the principle of keeping functions small?

Answer 1

I like the concept of 'one unit, one task'.

Let your function do exactly one clearly defined thing that can be expressed in a telling, shortish function name and doesn't need an overly large interface.

Answer 2

My methods/functions have not much to do:
* do something with a value
* return it or print it

If the method needs a lot of calculations or other stuff then I write a method for the method. I think this keeps the code readable.

Diego Lol :D

Answer 3

Where is it claimed that it is 3?

Answer 4

For readability and effectiveness

Answer 5

Why not four? Why not two?

Answer 6

Why not forty-two?

Answer 7

Diego, that would with necessity lead to less objections!

Answer 8

Jason, asking for three doesn't mean they are only three, they might be more. To me, it's the same as to say, "Give me five coding languages?" And you know that out of thirteen, you only give five.
By the way, the three I can give are, readability, understandability and testability