This. The problem with the Shakespeare argument is that authors compares code to artistic writing. But code should be compared to technical writing. When you write technical analysis or documentation, you are expected to create easily understood document that is tailored for the reader. Even if you really enjoy Joyce, you usually do not do your technical writing in Finnegans Wake style. That would be a terrible practice.
It is similar with code. People are writing obscure code for various reasons (trying to break the language, code golfing, etc.), but when you write code for a project that is to be maintained in the future, you should use the "formal" style of coding. This also means using the best practices and patterns that other people are accustomed to so they can be more effective.
Yeah, we shouldn't compare code to literary text or poetry, since these texts are not malleable in the way we want code to be.
For example Shakespeare often uses obsolete words or words which have changed meaning - but we can't replace these with more modern words or phases, since then it would break the meter or rhyme and destroy some of the double meanings. This is not a quality we want for code. We want code to be maintainable.
Perhaps this is the reason why pure FP is just as obscure as it is? Sure, it's technically more beautiful and pure and stuff, like a piece of art -- but a bunch of Java is easier to figure out, because it's plain as a cloth sack.
There's no reason "pure FP" should be fundamentally any more inscrutable than Java code; that assumption may just be a personal bias due to familiarity. It's definitely possible to go the other way too, with an object-oriented mess where a judicious application of functional principles would make for much clearer code.
It is similar with code. People are writing obscure code for various reasons (trying to break the language, code golfing, etc.), but when you write code for a project that is to be maintained in the future, you should use the "formal" style of coding. This also means using the best practices and patterns that other people are accustomed to so they can be more effective.