I think the issue is whether the functions that are split out are actually useful abstractions. If they are, you should not have to jump around the code-base,

I think the issue is whether the functions that are split out are actually useful abstractions. If they are, you should not have to jump around the code-base, you should be able to just read the invocation and know what it does, without leaving the source function. As an example, you probably don't whip out your kernel source code when you encounter a call to write(). At least not usually. You just know what it does and can keep going. You probably also don't look at the generated assembly code, and maybe look up the instruction reference for your favorite microprocessor when you encounter an arithmetic operator. You just assume that you know what it does, even if that may not be 100% correct in every case. Those are good, useful abstractions. That's what we need to strive for when we crate code.