How to stop functional programming

My methodology for avoiding this confusing “functional” programming: 1. Write: function add (a, b) { return a + b; } 2. Refactor to object: class AccumulatingIntegerWidget { constructor (...numbers) { this.accumulation = 0; this.accumulate(...numbers); } accumulate (...numbers) { for (const n of numbers) { this.accumulation = this.accumulation + n; } } getAccumulation () { return this.accumulation; } } Presto! It’s stateful and object-oriented and handles future cases like adding three numbers, even though…

Beyond the satire, one is supposed to write code which is readable, and like often with written works, one has to think about the "audience", the readers. When you write technical documentation, you have to decide ahead of time the expected skill level of the reader - often that decision is written too in the intro as "prerequisite(s)". When writing code you have the motto "don't make me think" in mind, but how to know what's the maximum level of…