> points he makes really don't translate to the software engineering world
His advice is in the context of functional programming languages. F#, Scala and even Haskell and OCaml are now very much part of the software engineering world (albeit a small part).
> How do you organise the interaction of libraries? You can do it yourself but you will have to follow some sort of pattern to organise the code
Because libraries compose, there's nothing to prevent a library on top of all these others libraries to accomplish this. If you have to repeat yourself with "patterns", your language of choice is failing you.
His advice is in the context of functional programming languages. F#, Scala and even Haskell and OCaml are now very much part of the software engineering world (albeit a small part).
> How do you organise the interaction of libraries? You can do it yourself but you will have to follow some sort of pattern to organise the code
Because libraries compose, there's nothing to prevent a library on top of all these others libraries to accomplish this. If you have to repeat yourself with "patterns", your language of choice is failing you.