> It makes local chunks of code (e.g. for loops) a bit harder to read but gives the reader a better sense of the wider context (e.g. a function or set of relate

> It makes local chunks of code (e.g. for loops) a bit harder to read but gives the reader a better sense of the wider context (e.g. a function or set of related functions). This, I believe, is a good trade-off because, in programming, the wider the context one is considering, the harder it is to gain a good understanding of that context. My style made understanding local context easier but made it noticeably harder to understand wider contexts. I wish I could remember in which thread I found a similar comment here within the last week or so. Painfully-heavily paraphrased, they said that a narrative/shorter function style of programming makes it easier to understand the intent of the logic/individual functions but harder to follow the overall flow, because you tend to have to jump frequently between functions in different parts of the file.