Or, how little can you make the reader have to think and still be able to really understand the code? There's a sweet spot there, where either simpler (or more simplistic) or more complicated is a net loss to the reader.

The problem is, the location of the sweet spot depends on the reader (or at least, on their familiarity with the idioms used...)