Thanks for your feedback. That I what I am trying to highlight. You can write similar code based on your needs. You don’t need to follow certain standards. For some, developer they like more concise code than well-structured code. I prefer the second part. Coz I love functional programming. So that is natural.
Regarding, the private variable I just highlighted. You may not need this now. With the help of a new private scope variable. Underscore will be going to obsolete. And more than it helps, it creates confusion. If you dont use it correctly.
Chris Tanner
For #4 your 'break down' code is much easier than your concise reducer code. It has good comments, good variable names, etc. It's much easier to read. We aren't charged by lines of code, and the less complex code is the less chance of introducing bugs.
Private variable naming also costs nothing and may prevent bugs.