We had another post on this topic the other day and my position is obviously the same. I've been programming for 35 years and the clearest long term trend is that I write shorter functions (notwithstanding starting out as a child in some random BASIC dialect where I wasn't taught about GOSUB, if it was even supported) and am more happy with my code.
If you have to argue against long function names to make small functions sound bad, you've already lost. In the other thread, I showed off some code from the main module of my current project, `bbbb`. Currently, the file contains 17 functions, of which 4 are hooks mandated by the calling code and the other 13 are private implementation details. The longest name in those implementation functions (`_normalized_name_and_version`) is the same length as the longest names among the hooks implemented (`get_requires_for_build_sdist` and `get_requires_for_build_wheel`), and would be shorter without the handicap of a leading underscore.
I'd say more, but it deserves more thought and editing than I want to devote to a comment submission form.
If you have to argue against long function names to make small functions sound bad, you've already lost. In the other thread, I showed off some code from the main module of my current project, `bbbb`. Currently, the file contains 17 functions, of which 4 are hooks mandated by the calling code and the other 13 are private implementation details. The longest name in those implementation functions (`_normalized_name_and_version`) is the same length as the longest names among the hooks implemented (`get_requires_for_build_sdist` and `get_requires_for_build_wheel`), and would be shorter without the handicap of a leading underscore.
I'd say more, but it deserves more thought and editing than I want to devote to a comment submission form.