Now the first real fight. Two well-known authors argued this out in writing, over months, and neither of them won.
Small functions
Also called Method length, One Thing
The advice that functions should be short, so each does one thing and has a name that says what. How short is where people stop agreeing. One famous book says very short. Another says too short makes code harder to read.
Splitting is mechanical, so an agent told to shrink functions can keep going without limit, and the numbers improve whether the code got clearer or not. Someone has to decide when to stop, and for now that is you.
Say it to your agent
“Split this function only where the new piece hides something its caller no longer has to think about. Don't create helpers that share module-level variables. If I would have to read two functions together to follow either one, keep them as one.”