It's like saying you need a reason not to add 4000 random jumps in your assembly code just to make it more difficult to read...
Source code tends to be very far removed from how computers execute anything, so I wouldn't use that as a justification for any sort of code style.
It is pronounced "documentation".
what we don't know is if it would have been possible to abstract those assumptions away so that functions could have been defined without them.
My longest code is always image processing. It's usually too hard to break up for the sake of breaking up. There's nothing to reuse between the calls to filters/whatever.
The fact that it works well and reads well (when it does, as in the parent's case), is.
Aside from those factors what else would be against it? Dogma?