[klyrs]

I see some truth to this, under a more reasonable interpretation. Clearly, well-golfed k/j/q/apl isn't doing the reader any favors. On the other hand, unnecessarily verbose code can be just as tortuous as unnecessarily terse code. And when you're comparing apples to apples (e.g. same algorithm, same data structures), shorter code is somewhat correlated to better performance.

In terms of developer productivity, less code faster to write and faster to read. To a point. The sweet spot is the shortest code that's still easy to read & write.