For the most part, I agree with this. The biggest problems I've had at work have been due to constructs that were a neat idea but just add to the complexity of figuring out the application. Throw in a bunch of business-specific engineering terminology that is not defined anywhere for the development team, and it becomes a wicked PITA to learn.
However, the one-liner example and the chained English-sounding methods, I think might be taken the wrong way. Both can be done well.
However, the one-liner example and the chained English-sounding methods, I think might be taken the wrong way. Both can be done well.