Programmers by and large don't seem to understand the power of language primarily as a communication tool and the lessons around communication we ought to under

Programmers by and large don't seem to understand the power of language primarily as a communication tool and the lessons around communication we ought to understand. We think in solitary terms as if it is of primary importance how we write code individually instead of how we communicate with each other (and the machine). Patterns if done well give us a language to solve problems in sensible ways as teams. Instead, we worry about how patterns are named and argue over minutiae. We let things like "exceptions should only be used for exceptional behavior" distract us from effectively communicating with each other. Our industry sees things like FP, OOP, Design Patterns, etc. as an exercise in taxonomy when building software is an exercise in communication. It's like we are writing a novel, but we are more worried about the names and families of characters than the actual plot itself. That doesn't make for a good book and it doesn't make for good software.