> But if the broken up functions are named well enough like in the example above, then it shouldn't be necessary to see how it's implemented, unless you're trac

> But if the broken up functions are named well enough like in the example above, then it shouldn't be necessary to see how it's implemented, unless you're tracking down a bug. (Emphasis added.) Yeah, exactly. Tracking down a bug is one of the times that code clarity is most important, and over eager abstraction is most annoying.