Clean code does emphasize that the structure of the class file and layout of functions should strive to allow for the entire class file to be read in a single p

Clean code does emphasize that the structure of the class file and layout of functions should strive to allow for the entire class file to be read in a single pass from top to bottom. Though, I'd agree that is quite different when someone puts in a linter that requires 5 line methods and scatters the flow of logic. IMHO, "imperative shell with functional core" (which implies consistent levels of abstractions) is a follow up the book could really use. To another extent, I think small and controversial rules of thumb like "keep functions short" can easily be taken out of context. A refactoring I often see that can be done when methods are poorly broken up is class variables can be converted into local variables once some of the methods are inlined. The point of the small function is so that a developer can keep track of fewer moving parts in their head while reading. If the shattering into functions causes the class to have 30 class variables in order to support that, then it's very much a case of following the wrong heuristic. IIRC, clean code holds a highest priority on the developer only needing to keep track of 3-5 things at a given time (and pretty much everything else is in service of that goal)