>I'd much rather read one function top to bottom than have to jump into 7 nested function calls that are only called once.
Well, yeah, coz that's worse.
It decreases code cohesion (especially when those functions are stuck in files far away) and to little appreciable benefit.
>First, because there are no universal code principles
I think there are and good developers have a spidey sense about what they are and will usually agree but we've yet to culturally agree on what they are as an industry.
Moreover, some literature on the topic (e.g. Robert Martin) is very, very wrong.
Well, yeah, coz that's worse.
It decreases code cohesion (especially when those functions are stuck in files far away) and to little appreciable benefit.
>First, because there are no universal code principles
I think there are and good developers have a spidey sense about what they are and will usually agree but we've yet to culturally agree on what they are as an industry.
Moreover, some literature on the topic (e.g. Robert Martin) is very, very wrong.