Why do people never use regular words when describing functional programming concepts?<p>This was initially promising but, like every other "let me explain functional programming" write-ups, reduced to inscrutable babble before we make any headway.<p>Case in point: author starts talking about monadic composition before explaining what a monad is!<p>What would be helpful is avoiding functional programming terms, explaining concepts in everyday English (or non-FP terms) then labeling those concepts after the fact.<p>Maybe instead of functional composition, call it an array of functions that pass their return value to the next function in the array. Or a promise.