Any nesting and indirection burden the mental fatigue on understanding the code: nesting conditional statements, macros, functions, classes while it's necessary to use or we will have so many duplicated codes which also burden the mental fatigue anyway.
There was an extreme argument on a SNS recently that someone claimed that he prohibit nesting if in their work.
Shorter-lived Variables argument doesn't always work. One of the most horrible code I read use very short-lived variables:
val_2 = f(val),
val_3 = g(val),
...
It's Erlang. Because Erlang's apparent variable isn't a variable, but just a name bound to a term.
There was an extreme argument on a SNS recently that someone claimed that he prohibit nesting if in their work.
Shorter-lived Variables argument doesn't always work. One of the most horrible code I read use very short-lived variables:
val_2 = f(val), val_3 = g(val), ...
It's Erlang. Because Erlang's apparent variable isn't a variable, but just a name bound to a term.