I much prefer breaking problems down to the level where I can reason in terms of sets, algebras, and that sort of thing. It's much easier for my brain to rely on properties and the ability to substitute terms in equations than it is to reconstruct a giant state machine and execute it in my head. Much more so when we add concurrency to the mix.
At the end of the day though I don't think there's, "one true way."
IMHO that is a side effect of how we teach people how to program mixed in with orgs cargo culting acronyms and not the core concepts of ideas.
Want people in a large organization to ignore your ideas? Speak them out loud.
Want them to follow them as dogma? Write a blog post under a pseudonym.
I always try to write code like
fn foo() {
let foo = do_first_thing();
let bar = do_second_thing();
do_third_thing(foo, bar);
}whenever possible. Then you can see the abstract overview of what the code does at a glance, but you can drill down into the details if you need to.
An ability that is only valuable if it really is a procedure, some sequence of operations, rather than a function, some forming of a value. I'd agree that procedures should generally not be split up into subprocedures; a procedure has to be read from top to bottom, so factoring out subprocedures only makes it harder to understand. But a function can be understood without understanding the smaller functions that it calls, so breaking functions up into smaller functions - and breaking small functions out of procedures, where possible - makes it easier to understand.
Having a language that makes an explicit distinction between procedures and functions - in particular, where calling a procedure looks different from calling a function - helps a lot (e.g. Haskell).
But in my domain I have seen countless one-line functions used in one place each, and it’s frustrating having to jump around the code (and add to my mental context stack*) rather than just putting some curly braces and a comment. Functions aren’t primarily meant as a hygiene mechanism. I really like the curly brace scoping in Rust.
I found my style partly by reading John Carmack and Casey Muratori’s coding philosophies and putting them to the test for myself.
* For a natural language analogy, consider the difference between parenthetical remarks and asterisks. You have to remember your place in the text.