In On Coding Standards and Code Reviews, I summarized this sentiment in two rules:

• Correctness, simplicity and clarity come first. Don't be a clever-dick.
• If you must rely on cleverness, encapsulate and comment it.

That is, I don't think you should ban cleverness, just discipline, comment and encapsulate it, so that your code base can be successfully maintained by a succession of many different programmers, with varying talents, over a period of many years.